[webkit-changes] [WebKit/WebKit] 1515a2: Make getName should return DOMString? instead of D...
Ryosuke Niwa
noreply at github.com
Tue Jun 6 18:51:02 PDT 2023
Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 1515a23b954f8ba0fba56b97fb9ba697833ccab2
https://github.com/WebKit/WebKit/commit/1515a23b954f8ba0fba56b97fb9ba697833ccab2
Author: Ryosuke Niwa <rniwa at webkit.org>
Date: 2023-06-06 (Tue, 06 Jun 2023)
Changed paths:
M LayoutTests/imported/w3c/web-platform-tests/custom-elements/CustomElementRegistry-expected.txt
M LayoutTests/imported/w3c/web-platform-tests/custom-elements/CustomElementRegistry.html
M Source/WebCore/dom/CustomElementRegistry.cpp
M Source/WebCore/dom/CustomElementRegistry.h
M Source/WebCore/dom/CustomElementRegistry.idl
Log Message:
-----------
Make getName should return DOMString? instead of DOMString or undefined
https://bugs.webkit.org/show_bug.cgi?id=257759
Reviewed by Chris Dumez.
Update the implementation of CustomElementsRegistry.prototype.getName to match the latest PR.
Namely, it now returns DOMString? instead of (DOMString or undefined):
https://github.com/whatwg/html/pull/9195
https://github.com/web-platform-tests/wpt/pull/39640
* LayoutTests/imported/w3c/web-platform-tests/custom-elements/CustomElementRegistry-expected.txt:
* LayoutTests/imported/w3c/web-platform-tests/custom-elements/CustomElementRegistry.html:
* Source/WebCore/dom/CustomElementRegistry.cpp:
(WebCore::CustomElementRegistry::getName):
* Source/WebCore/dom/CustomElementRegistry.h:
* Source/WebCore/dom/CustomElementRegistry.idl:
Canonical link: https://commits.webkit.org/264916@main
More information about the webkit-changes
mailing list