RESOLVED FIXED 255778
Add customElements.getName method
https://bugs.webkit.org/show_bug.cgi?id=255778
Summary Add customElements.getName method
Keith Cirkel
Reported 2023-04-21 04:37:46 PDT
I'm not sure if this is the right issue template, but I am trying to file implementer issues to get `customElements.getName()` defined. As a result of the WCCG F2F, the CG is interested in pursuing a method to get the name of a defined element. This is the result of that meeting. See https://github.com/WICG/webcomponents/issues/566 and https://github.com/whatwg/html/pull/9195 for more.
Attachments
Ryosuke Niwa
Comment 1 2023-04-21 15:42:22 PDT
EWS
Comment 2 2023-04-22 12:27:46 PDT
Committed 263281@main (e2748d7c56a2): <https://commits.webkit.org/263281@main> Reviewed commits have been landed. Closing PR #13053 and removing active labels.
Radar WebKit Bug Importer
Comment 3 2023-04-22 12:28:19 PDT
Thomas Wisniewski [:twisniewski]
Comment 4 2023-06-06 10:33:37 PDT
Pardon my ping of a closed bug, but I just tried to run the (not yet merged) WPTs from this patch on Safari Preview 171, and they aren't passing. I get this failure for all of the tests: assert_equals: expected (object) null but got (undefined) undefined Is this expected?
Ryosuke Niwa
Comment 5 2023-06-06 12:10:04 PDT
(In reply to Thomas Wisniewski [:twisniewski] from comment #4) > Pardon my ping of a closed bug, but I just tried to run the (not yet merged) > WPTs from this patch on Safari Preview 171, and they aren't passing. I get > this failure for all of the tests: > > assert_equals: expected (object) null but got (undefined) undefined > > Is this expected? Yes, that's expected. That semantics changed after I had landed WebKit code change. Will update WebKit's implementation shortly.
Note You need to log in before you can comment on or make changes to this bug.