Skip to content
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

[0.8] Listening to events on an element produces different results under ShadowDOM v. ShadyDOM #1284

Closed
sorvell opened this issue Mar 11, 2015 · 1 comment
Assignees
Labels

Comments

@sorvell
Copy link
Contributor

sorvell commented Mar 11, 2015

This is due to event retargeting. We'll need an api (perhaps part of Polymer.dom) to normalize the behavior. It should probably include both the target as seen in ShadyDOM (event.path[0]) and a normalized event.path.

@sorvell sorvell added the 0.8 label Mar 11, 2015
@sorvell sorvell self-assigned this Mar 11, 2015
@sorvell
Copy link
Contributor Author

sorvell commented Mar 16, 2015

Fixed via 739de80.

@sorvell sorvell closed this as completed Mar 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant