Bug Tracker

Opened 12 years ago

Closed 12 years ago

#9951 closed bug (fixed)

Wrong order in .trigger() when DOM is modified in a handler

Reported by: dmethvin Owned by: dmethvin
Priority: low Milestone: 1.7
Component: event Version: 1.6.2
Keywords: Cc:
Blocked by: Blocking:


The W3C DOM Event Model spec (http://www.w3.org/TR/DOM-Level-3-Events/#event-flow) says browsers are supposed to calculate the event propagation path in advance, so that modifications to the DOM in a handler does not affect the path. Although the liveHandler method attempts this for delegated events, .trigger() does not.


There are still some situations where delegated events may yield a different path than directly attached ones; need to document that.

Change History (2)

comment:1 Changed 12 years ago by dmethvin

Component: unfiledevent
Milestone: None1.7
Owner: set to dmethvin
Priority: undecidedlow
Status: newassigned

comment:2 Changed 12 years ago by Dave Methvin

Resolution: fixed
Status: assignedclosed

Fix #9951. Precompute path for .trigger() to match up with W3C spec.

Changeset: ecd10464e8659b008e52161cc029f9d6863e33b3

Note: See TracTickets for help on using tickets.