Implement custom elements API 
https://bugs.webkit.org/show_bug.cgi?id=154907
Summary Implement custom elements API
Ryosuke Niwa
Reported 2016-03-01 21:45:31 PST
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
Comment 1 2016-03-01 21:46:21 PST
<rdar://problem/19467099>
Ryosuke Niwa
Comment 2 2018-08-01 17:54:12 PDT
*** Bug 187907 has been marked as a duplicate of this bug. ***
Philip Jägenstedt
Comment 3 2020-04-08 01:30:59 PDT
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
Comment 4 2020-04-08 18:17:19 PDT
(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
Comment 5 2020-04-17 01:07:55 PDT
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.
Note You need to log in before you can comment on or make changes to this bug.