This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Ok, I open this bug to report inaccuracies that still exist in this table. Please don't close before finish spec., anyone can add their comments and other adjustments. BTW, please do not totally rely on HTML5 table (http://www.w3.org/html/wg/drafts/html/master/index.html#events-0), because in some case this table missing target, like for abort event:). We have to search all specification for a specific event. === scroll event Please add Document to "Trusted Targets". Firefox, Chrome and IE support them, and this target is defined in "CSSOM View Module" http://dev.w3.org/csswg/cssom-view/#scrolling-0 === error event Please add Window to "Trusted Targets". When we make error in <script> this event is fired to Window (Firefox, Chrome, IE): http://www.w3.org/html/wg/drafts/html/master/webappapis.html#create-a-script HTML5 also list Worker objects (http://www.w3.org/html/wg/drafts/html/master/index.html#event-error) but I don't check this case. === blur and focus event Please add Window to "Trusted Targets". Its compatible with HTML5 (and support by Firefox, Chrome, IE). * focusin and focusout is not describe in HTML5 and probably less stable in browsers. Element will match as target, but for Window I can't geterate in Chrome and IE (Firefox still not suport this events). But if focusin and focusout are highly related to the focus event (before/after) then maybe should support the same target. === keydown and keyup Any real test when Document is as target?
For beforeinput: - Default Action: None (https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#event-types-list) - Default action: Update the DOM element (https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#event-type-beforeinput)
(In reply to spiritRKS1910 from comment #0) > Ok, I open this bug to report inaccuracies that still exist in this table. > Please don't close before finish spec., anyone can add their comments and > other adjustments. Well, I don't think our process lends itself to keeping this bug open. We will try to address all the inaccuracies that we find, but you should open new bugs or reactivate previous bugs as appropriate instead. Thanks for you continued reviews! > BTW, please do not totally rely on HTML5 table > (http://www.w3.org/html/wg/drafts/html/master/index.html#events-0), because > in some case this table missing target, like for abort event:). We have to > search all specification for a specific event. > > === > > scroll event > > Please add Document to "Trusted Targets". Firefox, Chrome and IE support > them, and this target is defined in "CSSOM View Module" > > http://dev.w3.org/csswg/cssom-view/#scrolling-0 Agree. I'll add this. > === > > error event > > Please add Window to "Trusted Targets". When we make error in <script> this > event is fired to Window (Firefox, Chrome, IE): > http://www.w3.org/html/wg/drafts/html/master/webappapis.html#create-a-script > > HTML5 also list Worker objects > (http://www.w3.org/html/wg/drafts/html/master/index.html#event-error) but I > don't check this case. Agree. I'll add this. > === > > blur and focus event > > Please add Window to "Trusted Targets". Its compatible with HTML5 (and > support by Firefox, Chrome, IE). > > * focusin and focusout is not describe in HTML5 and probably less stable in > browsers. Element will match as target, but for Window I can't geterate in > Chrome and IE (Firefox still not suport this events). But if focusin and > focusout are highly related to the focus event (before/after) then maybe > should support the same target. Sounds reasonable. I'll make this consistent among all the focus events. > === > > keydown and keyup > > Any real test when Document is as target? Already fixed in Bug 25448.
This has now been fixed in the latest Editor's draft: https://dvcs.w3.org/hg/dom3events/rev/db192f1f3c39