Closed Bug 676750 Opened 13 years ago Closed 13 years ago

Inline event listeners should come first in the listener list

Categories

(Core :: DOM: Events, defect)

Product:
Core
Component:
DOM: Events
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: bzbarsky, Unassigned)

References

(
URL
)

Details

The spec says (a bit down from the link target):

  All event handlers on an object, whether an element or some other object, and
  whether set to null or to a Function object, must be registered as event
  listeners on the object when it is created
....
  Event handlers therefore always run before event listeners attached using
  addEventListener().

I'm not going to do that in bug 659350 in the interests of sanity.
Spec bug.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
It doesn't matter in which way listeners are added, they are always called in the
order they are added.
(In reply to Olli Pettay [:smaug] from comment #1)
> Spec bug.

Have you filed?
Not yet since I hadn't seen, and I was very surprised to see, this kind of 
text in the spec.
I guess I and others need to review 
http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#event-handlers
You need to log in before you can comment on or make changes to this bug.