[Bug 16332] stop propagation and canceled flags

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16332

--- Comment #6 from Travis Leithead [MSFT] <travil@microsoft.com> 2012-04-19 18:56:26 UTC ---
Based on the result from Comment 5, DOM3 Events needs to be updated in two
places for clarification:

(In reply to comment #0)
> says "As the final step of the event dispatch, for reasons of backwards  
> compatibility, the implementation must reset the event object's  
> internal-propagation and default-action-prevention states."
> 
> As far as I can tell this is not implemented this way. Propagation is not  
> reset in either Opera or WebKit (it is in Gecko).

The above spec comment needs to be removed from the event dispatch algorithm.
Something to its effect should be placed in the requirements for initEvent
which will be the only time that these internal state values will be reset.

(In reply to comment #5)
> [The "true" return value for dispatchEvent in IE can be partially explained by
> a critical reading of the prose under "Return Value" for dispatch event (**
> emphasis mine**):
> 
> | "Indicates whether **any of the listeners which handled the event**
> |  called Event.preventDefault(). If Event.preventDefault() was called
> |  the returned value must be false, else it must be true."
> 
> ...however, the value of defaultPrevented inside of the handler being "false"
> is clearly a bug without any backing from existing prose in DOM3 Events. :-)]

The prose under the Return Value for dispatchEvent will be tweaked to indicate
that preventDefault should be honored even if the caller used preventDefault
_before_ the event was dispatched (which is what implementations allow).

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 19 April 2012 18:56:29 UTC