This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The Shadow DOM ( http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html ) specification reads: "4.1 Upper-boundary Encapsulation To maintain the upper-boundary encapsulation, the following scoping constraints must apply to all nodes in a shadow tree: * The ownerDocument property refers to the document of the shadow host * The nodes and named elements are not accessible using shadow host's document DOM tree accessors or with Window object named properties * The nodes are not present in any of the document's NodeList, HTMLCollection, or DOMElementMap instances * The nodes with a unique id and named elements are not addressable from any attributes of elements in shadow host's document" This text leave possibility for shadow nodes with given id or name to be addressed from NodeList, HTMLCollection, or DOMElementMap properties of elements in shadow host's document. For example, the form element (http://www.w3.org/TR/html5/the-form-element.html#the-form-element ) define property of type HTMLFormControlsCollection. Named child element of the form can be accessed via form.elements.namedItem('child-id'). The specification do not clarify, whether the shadowed named child element should be accessible in such way.
These normative requirements need to be removed from the spec. They are confusing to implementers, test writers and developers. Duping against bug 20139. *** This bug has been marked as a duplicate of bug 20139 ***