-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web Components #60
Comments
FWIW, we've shipped parts of HTML Templates. |
Minor update:
|
Closing this per above. We'll file new issues as appropriate. |
We've shipped Shadow DOM and Custom Elements. Is there any reason to keep this open? |
We should document our positions in the table before closing issues. |
It seems like there are four pieces here:
It's also possible we need a position like |
This covers the four initial pieces of Web Components, as discussed in #60. Some historical discussion can be found at https://hacks.mozilla.org/2014/12/mozilla-and-web-components/ and https://hacks.mozilla.org/2015/06/the-state-of-web-components/. Closes #60.
This covers the four initial pieces of Web Components, as discussed in #60. Some historical discussion can be found at https://hacks.mozilla.org/2014/12/mozilla-and-web-components/ and https://hacks.mozilla.org/2015/06/the-state-of-web-components/. Closes #60.
This covers the four initial pieces of Web Components, as discussed in #60. Some historical discussion can be found at https://hacks.mozilla.org/2014/12/mozilla-and-web-components/ and https://hacks.mozilla.org/2015/06/the-state-of-web-components/. Closes #60.
I have split this into separate issues (see #1087): |
Raising this per suggestion from @dbaron in #59. I'm not really sure how to split this up since as per https://github.com/w3c/webcomponents/blob/gh-pages/README.md the situation is complicated.
On top of that there's various new proposals which @smaug---- and I should know more about next week (there's a meeting). My thinking is that we'll open issues for those proposals, but that for the above (apart from the CSS bits) we don't really need anything.
The text was updated successfully, but these errors were encountered: