Closed
Bug 1880890
Opened 1 year ago
Closed 1 year ago
[wpt-sync] Sync PR 44658 - Weird insertion
Categories
(Core :: DOM: Core & HTML, task, P4)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
125 Branch
| Tracking | Status | |
|---|---|---|
| firefox125 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 44658 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/44658
Details from upstream follow.
Anthony Ramine <n.oxyde@gmail.com> wrote:
Weird insertion
| Assignee | ||
Updated•1 year ago
|
Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core
| Assignee | ||
Comment 1•1 year ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=8e972a1136544a9d45da2779cc2b556438f208c2
| Assignee | ||
Comment 2•1 year ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 12 tests and 1 subtests
Status Summary
Firefox
OK : 12
PASS: 10
FAIL: 9
Chrome
OK : 12
PASS: 17
FAIL: 2
Safari
OK : 12
PASS: 6
FAIL: 13
Links
Details
Firefox-only Failures
- /dom/nodes/insertion-removing-steps/Node-appendChild-script-and-iframe.tentative.html [wpt.fyi]
- A script inserted atomically before an iframe (using a div) does not observe the iframe's contentWindow, since the 'script running' and 'iframe setup' both happen in order, after DOM insertion completes:
FAIL - A script inserted atomically before an iframe (using a DocumentFragment) does not observe the iframe's contentWindow, since the 'script running' and 'iframe setup' both happen in order, after DOM insertion completes:
FAIL - A script inserted atomically before an iframe (using a append() with multiple arguments) does not observe the iframe's contentWindow, since the 'script running' and 'iframe setup' both happen in order, after DOM insertion completes:
FAIL
- A script inserted atomically before an iframe (using a div) does not observe the iframe's contentWindow, since the 'script running' and 'iframe setup' both happen in order, after DOM insertion completes:
- /dom/nodes/insertion-removing-steps/Node-appendChild-script-and-style.tentative.html [wpt.fyi]
- An earlier-inserted <script> synchronously observes a later-inserted <style> (via a div) being applied:
FAIL
- An earlier-inserted <script> synchronously observes a later-inserted <style> (via a div) being applied:
New Tests That Don't Pass
- /dom/nodes/insertion-removing-steps/Node-appendChild-script-and-default-style-meta-from-fragment.tentative.html [wpt.fyi]
- Inserting <meta> that uses alternate stylesheets, applies the style during DOM insertion, and before script runs as a result of any atomic insertions:
FAIL(Chrome:FAIL, Safari:FAIL)
- Inserting <meta> that uses alternate stylesheets, applies the style during DOM insertion, and before script runs as a result of any atomic insertions:
- /dom/nodes/insertion-removing-steps/Node-appendChild-script-and-iframe.tentative.html [wpt.fyi]
- A script inserted atomically before an iframe (using a div) does not observe the iframe's contentWindow, since the 'script running' and 'iframe setup' both happen in order, after DOM insertion completes:
FAIL(Chrome:PASS, Safari:PASS) - A script inserted atomically before an iframe (using a DocumentFragment) does not observe the iframe's contentWindow, since the 'script running' and 'iframe setup' both happen in order, after DOM insertion completes:
FAIL(Chrome:PASS, Safari:PASS) - A script inserted atomically before an iframe (using a append() with multiple arguments) does not observe the iframe's contentWindow, since the 'script running' and 'iframe setup' both happen in order, after DOM insertion completes:
FAIL(Chrome:PASS, Safari:PASS)
- A script inserted atomically before an iframe (using a div) does not observe the iframe's contentWindow, since the 'script running' and 'iframe setup' both happen in order, after DOM insertion completes:
- /dom/nodes/insertion-removing-steps/Node-appendChild-script-and-style.tentative.html [wpt.fyi]
- An earlier-inserted <script> synchronously observes a later-inserted <style> (via a div) being applied:
FAIL(Chrome:PASS, Safari:PASS) - An earlier-inserted <script> synchronously observes a later-inserted <style> (via a DocumentFragment) being applied:
FAIL(Chrome:PASS, Safari:FAIL) - Earlier-inserted <script> (via a DocumentFragment) synchronously observes a later-inserted <link rel=stylesheet>'s CSSStyleSheet creation:
FAIL(Chrome:PASS, Safari:FAIL) - Earlier-inserted <script> (via a div) synchronously observes a later-inserted <link rel=stylesheet>'s CSSStyleSheet creation:
FAIL(Chrome:PASS, Safari:FAIL) - Earlier-inserted <script> (via a append()) synchronously observes a later-inserted <link rel=stylesheet>'s CSSStyleSheet creation:
FAIL(Chrome:PASS, Safari:FAIL)
- An earlier-inserted <script> synchronously observes a later-inserted <style> (via a div) being applied:
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/da8d6ac0ea4c
[wpt PR 44658] - DOM: Added a few batch-insertion scenarios that are incompatible across engines, a=testonly
https://hg.mozilla.org/integration/autoland/rev/81057f5a8410
[wpt PR 44658] - Update wpt metadata, a=testonly
Comment 4•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/da8d6ac0ea4c
https://hg.mozilla.org/mozilla-central/rev/81057f5a8410
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox125:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 125 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•