Skip to content

Loading…

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

Closed
sorvell opened this Issue · 0 comments

1 participant

@sorvell
Owner

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
@sorvell sorvell self-assigned this
@sorvell sorvell closed this issue from a commit
@sorvell sorvell Fixes #2081: make Polymer.dom(element).getDistributedNodes and Polyme…
…r.dom(element).getDestinationInsertionPoints() always return at least an empty array (was generating exception under Shadow DOM); make element.getContentChildNodes and element.getContentChildren always return at least an empty array when a selector is passed that does not find a <content> (was generating exception under Shadow DOM)
f966381
@sorvell sorvell closed this in f966381
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.