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 8630 - 6.5.6.1 If I'm reading the paragraph that begins "All event handlers on an element, whether set to null.." correctly, it means that event handling code registered with an IDL or content attribute always runs before any code registered with addEventListene
Summary: 6.5.6.1 If I'm reading the paragraph that begins "All event handlers on an el...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-04 19:29 UTC by contributor
Modified: 2010-10-04 14:49 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-01-04 19:29:59 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#events

Comment:
6.5.6.1 If I'm reading the paragraph that begins "All event handlers on an
element, whether set to null.." correctly, it means that event handling code
registered with an IDL or content attribute always runs before any code
registered with addEventListener.  If so, I think this is worth calling out in
a Note below that paragraph.  Also, I have no idea what the existing 2nd note
"The interfaces implemented by the event object..." means.

Posted from: 71.20.129.201
Comment 1 Ian 'Hixie' Hickson 2010-01-06 11:03:58 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: Partially Accepted
Change Description: see diff given below
Rationale: I added the note. Not sure what to do about the second note you mention; I don't know how to make it clearer. It's trying to say that the Function object assigned to the event handler attribute is not the value passed to addEventListener, because the listener is only registered once, and it does various magic things in addition to calling the Function object (e.g. handling the return value).
Comment 2 contributor 2010-01-06 11:04:33 UTC 
Checked in as WHATWG revision r4521.
Check-in comment: Lots of rewriting of the event handler attributes stuff: remove mention of namespaces, clarify some notes, clarify when the listeners are registered, clean up some class=impl usage.
http://html5.org/tools/web-apps-tracker?from=4520&to=4521