Upstreaming Custom Elements and Outstanding v1 #664
Labels
Comments
|
I removed the detailed checklist as every section in Custom Elements is already upstreamed. There's just some remaining things that need to be fixed. Hope that's okay. Will make a couple further tweaks. |
|
More than ok @annevk. Tweak away! The due diligence was actually a needed exercise (stored personal copy). I would have been cool even with a close. What is the next step after that? Assuming updating html & dom spec respectively where needed? Are there links to this where we can ref this issue? Thanks in advance. |
|
I'm not sure I understand. The main purpose of this issue as I see it is to inform those interested of the work that remains to be done on custom elements v1. |
4 tasks
teoli2003
pushed a commit
to mdn/browser-compat-data
that referenced
this issue
Dec 3, 2017
* Editorial: Add CustomElementRegistry platform support
- [x] √ CustomElementRegistry` Basic support
- [ ] √ CustomElementRegistry.define()` support
- [ ] √ CustomElementRegistry.get()` get
- [ ] √ CustomElementRegistry.whenDefined()` whenDefined
Addresses:
- WICG/webcomponents#664
Related MDN Documentation:
- `CustomElementRegistry.define()` - https://developer.mozilla.org/en-US/docs/Web/API/CustomElementRegistry/define
- `CustomElementRegistry.get()` - https://developer.mozilla.org/en-US/docs/Web/API/CustomElementRegistry/get
- `CustomElementRegistry.whenDefined()` - https://developer.mozilla.org/en-US/docs/Web/API/CustomElementRegistry/whenDefined
References:
- https://caniuse.com/#feat=custom-elementsv1
- Chrome Status - http://www.chromestatus.com/feature/4696261944934400
- Firefox Status - https://platform-status.mozilla.org/#custom-elements
- Webkit Status - http://webkit.org/status.html#feature-custom-elements
- Edge Status - http://status.modern.ie/customelements
Notes:
- Firefox flag status - https://bugzilla.mozilla.org/show_bug.cgi?id=889230#c9
* Editorial: Remove description from interface level
Addresses:
- #623 (comment)
* Editorial: Fix Chrome versions and notes
Addresses:
- #623 (comment)
* Editorial: Add additional restriction notes
Addresses:
- #623 (comment)
* Editorial: Remove empty lines
Addresses:
- #623 (comment)
* Editorial: Update entry order
Addresses:
- #623 (comment)
* Editorial: Fix opera_android notes
Addresses:
- #623 (comment)
* Editorial: CustomElementRegistry Set flags for firefox
References:
- https://github.com/mdn/browser-compat-data/blob/master/compat-data-schema.md#flags
* Convert flags to flag
* Editorial: Remove note from CustomElementRegistry firefox support
Addresses:
- #623 (comment)
|
This work has been completed. |
|
@rniwa thank you so much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related: #661 (nay #377, #495)
Standard: https://w3c.github.io/webcomponents/spec/custom/
Outstanding Issues in DOM and HTML:
Outstanding Issues in This Repository:
Current Vendor Status:
Google Chrome (shipped
#594918)Mozilla Firefox (in progress
#889230)Safari (autonomous CE only) (resolved/fixed
#150225)Opera (shipped
#594918)Edge (Under Consideration)
Internet Explorer (Not Supported)
Also have taken the liberty to update MDN Browser Compatibility for Custom Elements
as they still reflected Custom Elements v0 vendor status. From adopter feedback was causing some confusion in the wild:MDN CustomElementRegistry.define()matrixMDN CustomElementRegistry.get()matrixMDN CustomElementRegistry.whenDefined()matrixI hope this at least helps initiate moving forward.
Peace ☮️
The text was updated successfully, but these errors were encountered: