Closed Bug 1556697 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 17162 - custom-elements: Add a test for upgrade failure due to non-null shado…

Categories

(Core :: DOM: Core & HTML, defect, P4)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla69
Tracking Flags:
Tracking Status
firefox69 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync upstream])

Sync web-platform-tests PR 17162 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/17162
Details from upstream follow.

Kent Tamura <tkent@chromium.org> wrote:

custom-elements: Add a test for upgrade failure due to non-null shado…

…w root and disabledFeatures

Specification PR: https://github.com/whatwg/html/pull/4673

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core
Failed to get results from try push
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/d029a500f958
[wpt PR 17162] - custom-elements: Add a test for upgrade failure due to non-null shado…, a=testonly

https://hg.mozilla.org/mozilla-central/rev/d029a500f958

Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox69: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Whiteboard: [wptsync downstream] → [wptsync upstream]
You need to log in before you can comment on or make changes to this bug.