Wrong order in .trigger() when DOM is modified in a handler
|Reported by:||dmethvin||Owned by:||dmethvin|
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 5 years ago by dmethvin
- Component changed from unfiled to event
- Milestone changed from None to 1.7
- Owner set to dmethvin
- Priority changed from undecided to low
- Status changed from new to assigned