1419309 - Fix custom element WPT failures at Document.html

Status: RESOLVED FIXED

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

Description

[John Dai[:jdai]]

There are remains 3 test failures at Document.html[1][2][3].

[1] https://searchfox.org/mozilla-central/rev/919dce54f43356c22d6ff6b81c07ef412b1bf933/testing/web-platform/tests/custom-elements/reactions/Document.html
[2] https://searchfox.org/mozilla-central/rev/919dce54f43356c22d6ff6b81c07ef412b1bf933/testing/web-platform/meta/custom-elements/reactions/Document.html.ini
[3] http://w3c-test.org/custom-elements/reactions/Document.html

Comment 1

[John Dai[:jdai]]

It seems like we can't get definition from parser[1] when document.write[ln] a custom element in iframe, so willExecuteScript is false,  it'll not run custom element constructors. However, it works fine in non-iframe case.

[1] https://searchfox.org/mozilla-central/rev/9f3bd430c2b132c86c46126a0548661de876799a/parser/html/nsHtml5TreeOperation.cpp#414-415

Comment 2

[Edgar Chen [:edgar] (PTO until 02/09)]

(In reply to John Dai[:jdai] from comment #1)
> It seems like we can't get definition from parser[1] when document.write[ln]
> a custom element in iframe

The custom elements registry is replaced after document.open() call [1], and there is a spec discussion: https://github.com/whatwg/html/issues/1698#issuecomment-298748641.

[1] https://searchfox.org/mozilla-central/rev/be78e6ea9b10b1f5b2b3b013f01d86e1062abb2b/dom/html/nsHTMLDocument.cpp#1681-1683

Comment 3

[Edgar Chen [:edgar] (PTO until 02/09)]

File https://github.com/w3c/web-platform-tests/issues/8528.

Comment 4

[Edgar Chen [:edgar] (PTO until 02/09)]

Fixed and merged in upstream; https://github.com/w3c/web-platform-tests/pull/8529.