Skip to content
This repository has been archived by the owner on Apr 11, 2024. It is now read-only.

CustomElements V1 #501

Closed
WebReflection opened this issue Apr 4, 2017 · 7 comments
Closed

CustomElements V1 #501

WebReflection opened this issue Apr 4, 2017 · 7 comments

Comments

@WebReflection
Copy link

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.

chiefcll pushed a commit to chiefcll/html5test that referenced this issue Apr 10, 2017
@NielsLeenheer
Copy link
Collaborator

Should be fixed in the upcoming release of version 9.0

@WebReflection
Copy link
Author

same as modules, this version 9.0 ... I'm not sure it's shipped. Still no Custom Elements support for WebKit/GNOME Web

@NielsLeenheer
Copy link
Collaborator

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

@WebReflection
Copy link
Author

I can confirm it says yes now, but I can also tell you that HTML import can be removed because it's been decided that it won't be implemented cross browser.

@WebReflection
Copy link
Author

TL;DR WebComponents specification is:

  • Custom Elements V1
  • Shadow DOM
  • HTML templates

That's it

@WebReflection
Copy link
Author

should I open a new ticket and close this?

@WebReflection
Copy link
Author

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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants