Bug 154907
Ryosuke Niwa
Implement custom elements API:
https://www.w3.org/TR/custom-elements/
based on the consensus we've reached during Jan F2F:
https://rawgit.com/w3c/webcomponents/construction/spec/custom/index.html
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Ryosuke Niwa
<rdar://problem/19467099>
Ryosuke Niwa
*** Bug 187907 has been marked as a duplicate of this bug. ***
Philip Jägenstedt
I came across the tests for custom built-in elements in WPT:
https://wpt.fyi/results/custom-elements/builtin-coverage.html?run_id=478440003&run_id=484130003&run_id=461580002
This bug is about the custom elements API overall, is there a bug about built-in elements specifically?
Ryosuke Niwa
(In reply to Philip Jägenstedt from comment #3)
> I came across the tests for custom built-in elements in WPT:
> https://wpt.fyi/results/custom-elements/builtin-coverage.
> html?run_id=478440003&run_id=484130003&run_id=461580002
>
> This bug is about the custom elements API overall, is there a bug about
> built-in elements specifically?
That would be https://bugs.webkit.org/show_bug.cgi?id=182671 (with the resolution of WONTFIX).
Philip Jägenstedt
Thanks Ryosuke! I've linked to that bug in https://github.com/web-platform-tests/wpt-metadata/pull/145. It isn't displayed inline on wpt.fyi yet, but would in the future make it clear that these failures are associated with a closed bug and not a new/unknown failure.