Skip to main content

Bug Tracker

Side navigation

#13961 closed bug (invalid)

Opened May 29, 2013 01:21PM UTC

Closed June 13, 2013 08:54AM UTC

Last modified June 14, 2013 10:21AM UTC

stopImmediatePropagation does not work from inline event handler

Reported by: anonymous Owned by: anonymous
Priority: undecided Milestone: None
Component: unfiled Version: 1.10.0
Keywords: Cc:
Blocked by: Blocking:

When calling #stopImmediatePropagation() from an inline event handler, the event is still dispatched to registered event handlers:

The cause for this is that a new event object is created in #dispatch() and #isImmediatePropagationStopped is lost.

Attachments (0)
Change History (3)

Changed May 30, 2013 01:13AM UTC by dmethvin comment:1

owner: → anonymous
status: newpending

When would you encounter this? jQuery.event.dispatch() shouldn't ever be entered with an event that has propagation stopped.

Changed June 13, 2013 08:54AM UTC by trac-o-bot comment:2

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Changed June 14, 2013 10:21AM UTC by anonymous comment:3

Your question doesn't make any sense to me. Did you take a look at the fiddle I provided?