- From: <bugzilla@jessica.w3.org>
- Date: Wed, 05 Dec 2012 05:01:28 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20243
Bug ID: 20243
Summary: Strengthen boundary between shadow host's document
elements and shadow tree nodes
Classification: Unclassified
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: Component Model
Assignee: dglazkov@chromium.org
Reporter: a.semenov@unipro.ru
QA Contact: public-webapps-bugzilla@w3.org
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 5 December 2012 05:01:31 UTC