Bugzilla – Bug 16337
Last modified: 2012-04-27 23:59:44 UTC
In most implementations initEvent() can be invoked after dispatch as well.
I am not sure why we should disallow that. If we do disallow that, it
unsetting the "trusted flag" does not make much sense, as that can never
be set in the first place for events an author has control over that are
not yet dispatched.
It also makes the "requirement" on Event.type twice using different
Anne van Kesteren
Ooops. Missed my header info...
PORT of TRACKER ISSUE-186...
On 3/4/11 10:21 AM, Anne van Kesteren wrote:
> In most implementations initEvent() can be invoked after dispatch as
> well. I am not sure why we should disallow that.
I believe pages use this to redispatch events....
Agree with allowing initEvent to be invoked after dispatch.
I'm looking through the spec to find places that say things to the contrary...
With the latest update today, I've resolved this issue so that initEvent can be invoked after dispatch for both trusted and untrusted events. I fixed the few places in the spec that were incongruent with this notion. This should now line up property with DOM4.