Current Status of Webcomponents

[snuggs]

Should probably keep an eye on this @brandondees @Robertchristopher @janz93 @mrbernnz @btakita @scottmacdowell.

2018 - WICG/webcomponents#763 (comment)

- [WHATWG customElementRegistry](https://html.spec.whatwg.org/multipage/custom-elements.html#customelementregistry)

• Reasoning for FF not accepting HTML Imports
• HTML Modules
• • HTML Modules WICG/webcomponents#645
    - https://github.com/w3c/webcomponents/blob/gh-pages/proposals/HTML-Imports-and-ES-Modules.md
• webcomponentsjs custom element extensions - here and here
• Incorporate Custom Elements in HTML directly? w3c/html#955
• Client side include feature for HTML whatwg/html#2791
• Standardize <template> variables and event handlers whatwg/html#2254
• https://lists.w3.org/Archives/Public/public-html/2017Jun/0017.html
• Implementing customized builtin elements. webcomponents/custom-elements#88
• Agenda for W3C TPAC 2017 (Web Components) WICG/webcomponents#641
• HTML Imports / Templates -
  https://gist.github.com/TakayoshiKochi/fdc1e72d4fd0bbdaf61e7f23779e9139

Proposal to improve the DOM creation api
github.com/whatwg/dom/issues/150
github.com/whatwg/dom/issues/477
lit-html
https://gist.github.com/WebReflection/fadcc419f5ccaae92bc167d8ff5c611b
lit/lit#32 (comment)

JSDOM

• Add custom element support jsdom/jsdom#2548

hyperhtml
https://viperhtml.js.org/hyperhtml
https://medium.com/@WebReflection/dom-handleevent-a-cross-platform-standard-since-year-2000-5bf17287fd38
https://twitter.com/WebReflection/status/877131029303230464

Mozilla Custom Elements (Shadow Dom)
https://bugzilla.mozilla.org/show_bug.cgi?id=1205323

[brandondees]

Thanks, I will try to keep up.

[snuggs]

No worries @brandondees I'll let you know where the 🔥 s are.

[icyc9]

Awesome. Will keep my eyes on this.

[snuggs]

@brandondees update from the last TPAC meeting. /cc @tmornini @btakita @kurtcagle https://www.w3.org/2017/11/10-webplat-minutes.html

[snuggs]

@brandondees @btakita @tmornini is=... attribute has some interesting ideas being flushed out. Algos fairly simple to reproduce in user land as well. Gives the ability to subclass existing elements. i.e. custom dropdown box with customized event loop hooks behind the scenes.

whatwg/html#3402

[snuggs]

web-platform-tests/wpt#9175
web-platform-tests/wpt#9147
@brandondees @btakita @tmornini ability to extend from native HTML Elements added! In WPT (Web Platform Tests). ALL Browsers MUST implement now.

@brandondees remember we had the discussion of whether or not to extend HTMLElement as @tmornini mentioned a while ago extenitions are best avoided if possible. The spec forced extensions

We implement the following:

Element `foo-bar`
// merely a factory that links the string name to the following class.
// then `.define (element)`s for current/future occurrences
//  and `.upgrade (element)`s existing.
(class extends HTMLElement {})

We had contemplated

Element `foo-bar`

(class { /* We'll extend for you */ })

In retrospect this is where being lazy (which is usually a great thing) becomes a footgun.