- From: Cameron McCormack <cam-www-dom@aka.mcc.id.au>
- Date: Wed, 23 Feb 2005 12:12:02 +1100
- To: www-dom@w3.org
Hi. Two things I want to mention/ask. 1. In DOM 3 Events, if there is a custom event that is being dispatched to a currentTarget that has listeners in different groups, then there doesn't seem to be a way to ensure that the event will stop only the current group. Here is some pseudo code for firing event handlers on each current target, which hopefully illustrates the problem: - For each matching listener on the current target: - If the current listener's group is in the set of stopped groups, continue with the next listener. - If the event is not custom, and stopPropagation() has been called on the event object, then: - Add the current listener's group to the set of stopped groups. - In an implementation dependent way, reset the propagationStopped flag in the event object. - If the event is custom and isPropagationStopped() returns true: - Add the current listener's group to the set of stopped groups. - Somehow reset the propagationStopped flag in the custom event object, but since there is no way to do this from the CustomEvent interface, this cannot be done. All subsequent event groups will therefore be stopped too, since isPropagationStopped() will still return true. 2. In DOM 3 Core's namespace normalization algorithm, it says to report an error if the namespace declaration is invalid. It doesn't say, though, what DOMError error string to use here. What should it be? (There are other instances of 'report an error' in the algorithm, with no appropriate error string, too.) Thanks, Cameron -- e-mail : cam (at) mcc.id.au icq : 26955922 web : http://mcc.id.au/ msn : cam-msn (at) aka.mcc.id.au office : +61399055779 jabber : heycam (at) jabber.org
Received on Wednesday, 23 February 2005 04:58:51 UTC