Side navigation
#13997 closed bug (fixed)
Opened June 06, 2013 04:53AM UTC
Closed March 13, 2014 01:45AM UTC
Last modified April 18, 2014 07:11PM UTC
stopImmediatePropagation doesn't stop DOM added event listeners
Reported by: | mark@glyphic.com | Owned by: | dmethvin |
---|---|---|---|
Priority: | low | Milestone: | 1.11.1/2.1.1 |
Component: | event | Version: | 1.10.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Calling stopImmediatePropagation()
will correctly stop other handlers set on the element from firing, but only those added with jQuery. Other handlers added with addEventListener()
will still fire.
To stop all immediate propagation from within a jQuery event handler, one must call both:
event.stopImmediatePropagation(); event.originalEvent.stopImmediatePropagation();
Calling stopImmediatePropagation()
on the jQuery event object should call it on the underlying DOM event object.
Attachments (0)
Change History (7)
Changed June 06, 2013 12:38PM UTC by comment:1
component: | unfiled → event |
---|---|
milestone: | None → 1.10.2/2.0.3 |
priority: | undecided → low |
status: | new → open |
Changed September 16, 2013 01:24AM UTC by comment:2
milestone: | 1.10.2/2.0.3 → 1.next |
---|
Changed September 16, 2013 08:10PM UTC by comment:3
We need a 1.next/2.next
milestone. This is not only a 1.x
issue.
Changed September 16, 2013 08:55PM UTC by comment:4
milestone: | 1.next → 1.next/2.next |
---|
Changed March 04, 2014 02:56PM UTC by comment:5
milestone: | 1.next/2.next → 1.11.1/2.1.1 |
---|---|
owner: | → dmethvin |
status: | open → assigned |
Changed March 13, 2014 01:45AM UTC by comment:6
resolution: | → fixed |
---|---|
status: | assigned → closed |
Event: Call underlying stopImmediatePropagation when present
Fixes #13997
Changeset: 6a89db86ed817f6a7498076e2a06b90f9fce0831
Changed April 18, 2014 07:11PM UTC by comment:7
summary: | stopImmediatePropagation doesn't stop DOM added event listenders → stopImmediatePropagation doesn't stop DOM added event listeners |
---|
Yep, seems to have been that way forever. Note that there is no way to stop immediate propagation in oldIE so this will introduce a difference in behavior of non-jQuery events in oldIE vs other browsers. (Perhaps consistency is why it was there?) It doesn't affect the 2.x branch due to its browser support list but it does affect 1.x.