Closed Bug 1437000 Opened 2 years ago Closed 2 years ago

[wpt-sync] PR 9437 - custom-elements: Element with a valid custom element name created by createElement(name, options) should be upgraded

Categories

(Core :: DOM: Core & HTML, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
mozilla61
Tracking Status
firefox61 --- fixed

People

(Reporter: wptsync, Unassigned)

Details

(Whiteboard: [wptsync downstream])

createElement('my-foo', {}) was not upgraded even though
createElement('my-foo') is upgraded. Document::CreateElement() should
set "undefined" state even if the local name is valid for Custom Element
V0.

Bug: 810289
Change-Id: If70c40d6de520fe79b73e7fb6b21d776e636fee9

Reviewed-on: https://chromium-review.googlesource.com/907912
WPT-Export-Revision: 68279bb8eb58e8477f2ddebaca68f7c211423f9a
Component: web-platform-tests → DOM
Product: Testing → Core
Priority: -- → P3
Ran 1 tests and 37 subtests
OK     : 1
PASS   : 33
FAIL   : 4

Existing tests that now have a worse result (e.g. they used to PASS and now FAIL):
/custom-elements/Document-createElement.html
    document.createElement must create an instance of autonomous custom elements when it has is attribute: FAIL
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f44838746399
[wpt PR 9437] - custom-elements: Element with a valid custom element name created by createElement(name, options) should be upgraded, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/31ff678912d2
[wpt PR 9437]- Update wpt metadata, a=testonly
https://hg.mozilla.org/mozilla-central/rev/f44838746399
https://hg.mozilla.org/mozilla-central/rev/31ff678912d2
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.