Implement Custom Elements v1 #1344

Open
opened 3 years ago by g4jc · 4 comments
g4jc commented 3 years ago (Migrated from github.com)
Owner

We have most of Custom Elements v0 in the tree, this was an evolving spec that has since moved on to v1. In order to be compatible with websites using Custom Elements v1, we need to update existing code.

https://developers.google.com/web/fundamentals/web-components/customelements

Blocks #1343 and #252

We have most of Custom Elements v0 in the tree, this was an evolving spec that has since moved on to v1. In order to be compatible with websites using Custom Elements v1, we need to update existing code. https://developers.google.com/web/fundamentals/web-components/customelements Blocks #1343 and #252
wolfbeast commented 3 years ago (Migrated from github.com)
Owner

Looks like we got lucky with Mozilla having something half-finished in our tree for once.
Can you indicate in which order all this is supposed to land? Does #1343 block this?

Looks like we got lucky with Mozilla having something half-finished in our tree for once. Can you indicate in which order all this is supposed to land? Does #1343 block this?
g4jc commented 3 years ago (Migrated from github.com)
Owner

Can you indicate in which order all this is supposed to land? Does #1343 block this?

Yes, while it may be possible to implement CE without <dialog>, landing #1343 first makes it much easier. Both cause changes in the HTML Tree Binding, so this will land later.

> Can you indicate in which order all this is supposed to land? Does #1343 block this? Yes, while it may be possible to implement CE without `<dialog>`, landing #1343 first makes it much easier. Both cause changes in the HTML Tree Binding, so this will land later.
mattatobin commented 3 years ago (Migrated from github.com)
Owner

Blocks #1361

Blocks #1361
g4jc commented 3 years ago (Migrated from github.com)
Owner

We definitely still need to land
customElements.define must upgrade custom element in shadow-including tree order
for web compat. Unfortunately without CSS selectors, testing will be problematic.

We definitely still need to land [ customElements.define must upgrade custom element in shadow-including tree order ](https://bugzilla.mozilla.org/show_bug.cgi?id=1326028) for web compat. Unfortunately without CSS selectors, testing will be problematic.
Moonchild modified the milestone from 29.0.0 to 30.0.0 2 years ago
Moonchild added the
Bounty
label 2 years ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MoonchildProductions/UXP#1344
Loading…
There is no content yet.