Open Bug 1419329 Opened 7 years ago Updated 2 years ago

Fix custom element WPT failures at Document-createElement.html

Categories

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

defect

Tracking

()

People

(Reporter: jdai, Unassigned)

References

(Depends on 2 open bugs, Blocks 2 open bugs)

Details

Priority: -- → P2
The failed case is something like, https://software.hixie.ch/utilities/js/live-dom-viewer/?saved=5600. It looks like an expected behavior in Gecko since we don't use the same prototype on the new wrapper after adoptNode() call, see bug 1081039 comment #9.
Priority: P2 → P3
Yeah, this can't really block CEv1, since this is about our prototype handling in general.
No longer blocks: 1419295
Severity: normal → S3
Blocks: 1528791

Now we have these below three failures according to wpt.fyi :
document.createElement must report a NotSupportedError when the element is adopted into a the document of an iframe during construction
document.createElement must report a NotSupportedError when the element is inserted into a the document of an iframe during construction
document.createElement must not report a NotSupportedError when the element is adopted back from a the document of an iframe during construction

I couldn't immediately see if these really depend on bug 1470017.
(Adam, would you kindly help check/correct the bug dependency?)

Depends on: 1502814
Flags: needinfo?(avandolder)

This bug has more of a direct dependency on bug 1502814. Bug 1470017 deals with prototypes in general (and would solve this issue), but bug 1502814 specifically is about the case of custom element prototypes, which based on the current patch discussion will likely need to be resolved without fixing the more general case.

Flags: needinfo?(avandolder)
You need to log in before you can comment on or make changes to this bug.