This repository has been archived by the owner on Apr 11, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 192
CustomElements V1 #501
Comments
chiefcll
pushed a commit
to chiefcll/html5test
that referenced
this issue
Apr 10, 2017
NielsLeenheer
added a commit
that referenced
this issue
May 14, 2017
Should be fixed in the upcoming release of version 9.0 |
same as modules, this version 9.0 ... I'm not sure it's shipped. Still no Custom Elements support for WebKit/GNOME Web |
Version 9 was a 'bit' delayed while I had to focus on other projects. But the next version is back on track and should released before Christmas. The fixed test is currently available on https://alpha.html5test.com |
I can confirm it says |
TL;DR WebComponents specification is:
That's it |
should I open a new ticket and close this? |
no answers in a while ... closing this for now, please drop HTML imports from scores. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Apparently there's only a V0 check like
'registerElement' in document
which would only score on Chrome.The current V1 specs, agreed by all vendors, should be checked as
'customElements' in window
instead, or"CustomElementsRegistry" in window
Thanks.
The text was updated successfully, but these errors were encountered: