-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
event.stopPropagation() no longer stops propagation after removing jQuery #17840
Comments
@chancancode Hi! What's going on there? |
@lolmaus I'm not sure yet, but I ran into the same issue with one of the built-in components, we just didn't notice it because the those haven't been running on CI without jquery, due to some config issues |
@simonihmig do you know if this is expected? |
I think at least part of the problem is that, the even is not technically "propagating" since it already propagated all the way to ember's root element at this point, so |
cancelBubble getter may work 🤔 |
Hm, so as mentioned to @lolmaus in private, returning
Regarding
Yes, that looks right, shouldn't be too hard then to fix, if we agree this needs to be fixed. |
Let's try to fix it! @simonihmig would you like to work on this? There is already a failing test that I "disabled" in #17847, but we should probably add more. |
I also briefly looked into the |
…g up when event.stopPropagation() was called Fixes emberjs#17840
@chancancode sure, here's a PR: #17874 😀 /cc @lolmaus |
Hi!
I've built and am maintaining the ember-drag-sort addon which happens to be the only drag-n-drop addon in the Ember ecosystem with support for nested lists.
It's been working fine with jQuery. Demo: https://kaliber5.github.io/ember-drag-sort/
I've tried upgrading to Ember 3.8 without jQuery and discovered that
event.stopPropagation()
no longer stops propagation. As a result, events on child lists get overridden by events on parent lists, and reordering nested lists no longer works.I've pushed the
gen-1
branch which is based on no-jQuery Ember 3.8. Here are some of problematic spots:(Note that in the latter spot I tried adding
event.preventDefault()
andreturn false
which didn't help and might have made things even worse, so it might make sense removing those when you try.)This looks like a regression in Ember to me, but I can't confirm it myself. Please help!
The text was updated successfully, but these errors were encountered: