Philip Jägenstedt b09ee9ecc3 Bug 1897147 [wpt PR 46309] - Map custom elements to two different features, a=testonly ...

Automatic update from web-platform-tests
Map custom elements to two different features (#46309)

This should match https://github.com/web-platform-dx/web-features/pull/1089.

The test results on wpt.fyi were used as a guide for where there might
be tests involving customized built-in elements, and all tests with
failures were given a quick review before deciding where to map it.
Mistakes are still possible.

This is the most complicated mapping to web-features so far, and shows
some limitations of the WEB_FEATURES.yml format. This could be
simplified with exclusion patterns in the format, but would still not be
simple.

Two files were renamed in the process of preparing this:
https://github.com/web-platform-tests/wpt/pull/46305
https://github.com/web-platform-tests/wpt/pull/46306
--

wpt-commits: d437c3d7a1bc22ac2cd0cc902ff5d891ae448e2d
wpt-pr: 46309

2024-05-30 07:56:06 +00:00

..

parser-constructs-custom-element-in-document-write.html

…

parser-constructs-custom-element-synchronously.html

…

parser-constructs-custom-elements-with-is.html

…

parser-constructs-custom-elements.html

…

parser-custom-element-in-foreign-content.html

…

parser-fallsback-to-unknown-element.html

…

parser-sets-attributes-and-children.html

…

parser-uses-constructed-element.html

…

parser-uses-create-an-element-for-a-token-svg.svg

…

parser-uses-registry-of-owner-document.html

…

serializing-html-fragments-customized-builtins.html

…

WEB_FEATURES.yml

…