This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13534 - 2.1.4 DOM Core versus DOM L3 Events reference
Summary: 2.1.4 DOM Core versus DOM L3 Events reference
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2011-08-02 22:31 UTC by Travis Leithead [MSFT]
Modified: 2011-09-20 15:21 UTC (History)
9 users (show)

See Also:


Attachments

Description Travis Leithead [MSFT] 2011-08-02 22:31:27 UTC
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.
Comment 1 Anne 2011-08-03 05:39:20 UTC
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.
Comment 2 Jacob Rossi [MSFT] 2011-08-03 05:54:00 UTC
(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.
Comment 3 Anne 2011-08-03 06:06:20 UTC
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.
Comment 4 Michael[tm] Smith 2011-08-04 05:17:18 UTC
mass-move component to LC1
Comment 5 Ian 'Hixie' Hickson 2011-08-22 22:25:41 UTC
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.
Comment 6 Michael Cooper 2011-09-20 15:21:06 UTC
Bug triage sub-team not sure if this is an accessibility issue, will ask HTML A11Y TF.