Skip to content
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

Closed
annevk opened this issue Mar 2, 2018 · 7 comments · Fixed by #227
Closed

Web Components #60

annevk opened this issue Mar 2, 2018 · 7 comments · Fixed by #227

Comments

@annevk
Copy link
Contributor

annevk commented Mar 2, 2018

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.

  • Shadow DOM: we're implementing "v1" and this is now part of the DOM and HTML standards. (Some parts ended up in CSS, UI Events, Touch Events.)
  • Custom elements: we're implementing "v1" and this is now part of the DOM and HTML standards.
  • HTML Templates: shipped and now part of the HTML standard.
  • CSS changes: I'm not sure what the status is here.
  • HTML Imports: this is now abandoned I think. We've opposed this in the past: https://hacks.mozilla.org/2014/12/mozilla-and-web-components/.

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.

@smaug----
Copy link
Collaborator

FWIW, we've shipped parts of HTML Templates.
https://bugzilla.mozilla.org/show_bug.cgi?id=1090513 is open

@dbaron dbaron added the venue: W3C Specifications in W3C Working Groups label Aug 9, 2018
@annevk
Copy link
Contributor Author

annevk commented Nov 12, 2018

Minor update:

@annevk
Copy link
Contributor Author

annevk commented Jun 24, 2019

Closing this per above. We'll file new issues as appropriate.

@annevk annevk closed this as completed Jun 24, 2019
@annevk annevk added the venue: WHATWG Specifications in a WHATWG Workstream label Jul 2, 2019
@annevk annevk reopened this Jul 2, 2019
@annevk annevk closed this as completed Jul 2, 2019
@annevk annevk reopened this Jul 2, 2019
@smaug----
Copy link
Collaborator

We've shipped Shadow DOM and Custom Elements. Is there any reason to keep this open?

@dbaron
Copy link
Contributor

dbaron commented Jul 2, 2019

We should document our positions in the table before closing issues.

@dbaron
Copy link
Contributor

dbaron commented Nov 21, 2019

It seems like there are four pieces here:

  • Shadow DOM - should we list this as important or something else?
  • Custom elements - same?
  • HTML Templates - same?
  • HTML Imports: seems like we should list this as harmful based on the info above, but we'd need an explanation of why. @annevk, would you be able to write that?

It's also possible we need a position like acceptable for something that's past the prototyping stage but not important? If we had such a position, would we want to use it here?

annevk added a commit that referenced this issue Nov 21, 2019
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.
annevk added a commit that referenced this issue Dec 4, 2019
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.
dbaron pushed a commit that referenced this issue Dec 7, 2019
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.
@zcorpan zcorpan added duplicate and removed venue: W3C Specifications in W3C Working Groups venue: WHATWG Specifications in a WHATWG Workstream position: positive labels Oct 15, 2024
@zcorpan
Copy link
Member

zcorpan commented Oct 15, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants