This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Here is the statement: "The existence of multiple DOM trees is enabled by letting any element in the document tree to host one or more additional DOM trees" And here is the test that passes with Chrome v22 and fails with Chrome v23: // check one or multiple shadows for more complex element (<iframe>) test(function () { var d = newHTMLDocument(); var n = d.createElement('iframe'); d.body.appendChild(n); var s1 = new SR(n); assert_equals(s1.ownerDocument, d, 'Check1 for s1.ownerDocument value'); var s2 = new SR(n); assert_equals(s2.ownerDocument, d, 'Check1 for s2.ownerDocument value'); assert_equals(s1.ownerDocument, d, 'Check2 for s1.ownerDocument value'); }, 'A_04_00_01_T02', PROPS(A_04_00_01, { author:'Mikhail Fursov <mfursov@unipro.ru>', reviewer:'' })); This either issue for spec or for chrome(webkit) v23
The error text is: [HIERARCHY_REQUEST_ERR: DOM Exception 3(stack: Error: A Node was inserted somewhere it doesn't belong. at Object.PROPS.author and the error is produced by var s1 = new SR(n); when n is a iframe node
The error message looks strange and unrelated, however test syntax is correct and passes with the following minor mod: ('new SR(n)' commented) // check one or multiple shadows for more complex element (<iframe>) test(function () { var d = newHTMLDocument(); var n = d.createElement('iframe'); d.body.appendChild(n); var s1 = {ownerDocument: d};//new SR(n); assert_equals(s1.ownerDocument, d, 'Check1 for s1.ownerDocument value'); var s2 = {ownerDocument: d};//new SR(n); assert_equals(s2.ownerDocument, d, 'Check1 for s2.ownerDocument value'); assert_equals(s1.ownerDocument, d, 'Check2 for s1.ownerDocument value'); }, 'A_04_00_01_T02', PROPS(A_04_00_01, { author:'Mikhail Fursov <mfursov@unipro.ru>', reviewer:'' }));
+ if you change 'iframe' to 'div' in the original test, the test starts to pass.
This is both a spec and an implementation issue. I need to raise this in the WG.
*** This bug has been marked as a duplicate of bug 18435 ***
See https://bugs.webkit.org/show_bug.cgi?id=90859 for implementation bug.