Bug 100332
| Summary: | [ShadowDOM]: Styles in shadow element presents in document.styleSheets collection | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Sergey G. Grekhov <sgrekhov> |
| Component: | DOM | Assignee: | Web Components Team <webcomponents-bugzilla> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | a.semenov, dglazkov, morrita, rniwa, shinyak, webcomponents-bugzilla |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Bug Depends on: | |||
| Bug Blocks: | 63606, 103230 | ||
Sergey G. Grekhov
Found in Chrome 22.0.1229.94 m
According Shadow DOM spacification styles added to the shadow element shouldn't be exposed via document.styleSheet collection (http://www.w3.org/TR/shadow-dom/#upper-boundary-encapsulation) but in fact these styles are visible. The following test fails:
var SR = window.ShadowRoot ||
window.WebKitShadowRoot;
var iframe = document.createElement('iframe');
iframe.src = 'resources/blank.html';
document.body.appendChild(iframe);
iframe.onload = function () {
try {
var d = iframe.contentDocument;
var s = new SR(d.head);
var style = d.createElement('style');
s.appendChild(style);
assert_equals(d.styleSheets.length, 0,
'style elements in shadow DOM must not be exposed via ' +
'the document.styleSheets collection');
} finally {
iframe.parentNode.removeChild(iframe);
}
};
blank.html in the test above is the simple page with the following HTML:
<!DOCTYPE html>
<html>
<head></head>
<body></body>
</html>
Please note that the similar tests for links (instead of style link to the css file is being created) works well. Exact code is:
var link = d.createElement('link');
link.setAttribute('rel', 'stylesheet');
link.setAttribute('href', 'testharness.css');
s.appendChild(link);
The link from the above is not visible via document.styleSheets collection
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Hajime Morrita
*** Bug 105274 has been marked as a duplicate of this bug. ***
Ryosuke Niwa
This has been fixed for v1 API.