13534 2011-08-02 22:31:27 +0000 2.1.4 DOM Core versus DOM L3 Events reference 2011-09-20 15:21:06 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC Windows NT RESOLVED WONTFIX a11y P3 normal --- 1 travil ian annevk ayg cooper eoconnor ian jrossi mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 52020 0 travil 2011-08-02 22:31:27 +0000 DOM L3 Events has appropriate descriptions for each of these behaviors, as well as a more complete discussion of other event-related information. Also, given DOM L3 Events is in a more more “stable” point along the REC track, it makes more sense to reference it. Referencing completed, stable standards is important for Microsoft and our customers (who build on top of our software). Existing Text: In the contexts of events, the terms fire and dispatch are used as defined in the DOM Core specification: firing an event means to create and dispatch it, and dispatching an event means to follow the steps that propagate the event through the tree. The term trusted event is used to refer to events that have the trusted flag set. [DOMCORE] Suggested change: Reference to DOM L3 Events here instead of Web DOM Core. 52091 1 annevk 2011-08-03 05:39:20 +0000 DOM 3 Events does not define the same algorithms and does not really have the same level of quality. I still think DOM 3 Events should just drop the bits on the event model and rename itself to UI events or some such. 52104 2 jrossi 2011-08-03 05:54:00 +0000 (In reply to comment #1) > DOM 3 Events does not define the same algorithms and does not really have the > same level of quality. I still think DOM 3 Events should just drop the bits on > the event model and rename itself to UI events or some such. I firmly believe DOM Core should not be specifying the event model while D3E continues to make progress towards Recommendation status. If you do not believe D3E is of sufficient quality, then you should submit additional feedback to the working group. Having two different specifications of the event model in competition is contrary to progress and makes it difficult for implementors and end developers to target an interoperable model. 52112 3 annevk 2011-08-03 06:06:20 +0000 Still waiting for replies to feedback I gave in March. DOM Core is making progress towards Recommendation too, so I am not sure that argument makes sense. 53781 4 mike 2011-08-04 05:17:18 +0000 mass-move component to LC1 55622 5 ian 2011-08-22 22:25:41 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: I think DOM Core is a superior reference to DOM Level 3 Events. 57035 6 cooper 2011-09-20 15:21:06 +0000 Bug triage sub-team not sure if this is an accessibility issue, will ask HTML A11Y TF.