-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[draggable] track draggable item scopes #9153
Conversation
Interesting. Do you know why removing angular debug info broke this? I'm curious why it worked with the debug info. Perhaps the debug code somehow stops the elements scope from being garbage collected? Makes me nervous that there are similar bugs, as yet unfound, that suffer the same problem. That PR is about a month old but if it took 30 days to realize we can't create any visualizations in non-dev mode.... there might be more issues lurking. What are your thoughts @spalger? |
This code was previously dependent on the I totally agree with the notion that this could indicate other undiscovered issues. I've verified that there isn't any other code (except tests) using the |
Are we polyfilling WeakMap? Support seems to be rather non-existent for IE 11. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap |
Yep, we use the core-js implementation by virtue of the babel-polyfill |
LGTM |
Ahah, I see now in the angular documentation about scope, though they aren't very clear that you shouldn't use it outside of debugging though:
Thanks for the explanation, lgtm! |
Backported to 5.1 in #9250 |
Fixes #9151
The bug described in #9151 is caused by the removal of the angular debug info in #7929. A second quick-fix option is to track the element scopes inside the draggable container with a
WeakMap()
.#9152 is an alternative solution