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

element.getContentChildNodes generates exception under Shadow dom when a content is not found #2081

Closed
sorvell opened this issue Jul 14, 2015 · 0 comments
Assignees
Labels

Comments

@sorvell
Copy link
Contributor

sorvell commented Jul 14, 2015

The element.getContentChildNodes(selector) generates an exception when run under Shadow DOM when the selector argument does not correspond to an existing <content> element. When run under Shady DOM, this returns an empty array. We should normalize this behavior.

The root cause is that Polymer.dom(element).getDistributedNodes generates an exception under Shadow DOM when element does not have this api. This should be normalized as well.

@sorvell sorvell added the p2 label Jul 14, 2015
@sorvell sorvell self-assigned this Jul 14, 2015
kevinpschaaf added a commit that referenced this issue Jul 15, 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