This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
(originally from 25295) Target for event type is not complete. I understand that you wrote: "When used with an [XML 1.0] or [HTML5] application, the specifications of those languages MAY restrict the semantics and scope (in particular the possible event targets) associated with an event type." But now we have different event target within the same specification: for event resize (https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#event-type-resize) we have defaultView but in event table (https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#h4_event-types-list) we have defaultView, Document.
These should be consistent. I'll add Document to the table where it is missing.
But better should be delete Document, not add, unless there is a case for Document. I can only say that in HTML this apply to: defaultView some Element (like video, maybe frames to), detail: https://bugzilla.mozilla.org/show_bug.cgi?id=992685 Similar for scroll, don't see any case when Document is a target. Maybe if we considering synthetic event then Document and Window will always, but everything that support EventTarget will always fit. Its depend what you want put on this table. If "List of DOM3 Event Types" has only "Trusted event target types" then other tables should have the same (only trusted). The same remark may apply to other properties, consider only trusted cases.
Simmilar for wheel event type: Target defaultView, Document, Element Any practical case where a trusted event is fired at defaultView or Document? All browser use only element (unless I omitted something).
Gary will be making this update as well...
Fixed as part of 25358. https://dvcs.w3.org/hg/dom3events/rev/40019b0b87c3 Document was removed where it wasn't appropriate for trusted events.