search

devpunks / snuggsi

snuggsi ツ - Easy Custom Elements in ~1kB
https://snuggsi.com
MIT License
395 stars 17 forks source link

Current Status of Webcomponents #71

Open snuggs opened 7 years ago

snuggs commented 7 years ago

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

2018 - https://github.com/w3c/webcomponents/issues/763#758

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

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 https://github.com/PolymerLabs/lit-html/issues/32#issuecomment-320800997

JSDOM

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 commented 7 years ago

Thanks, I will try to keep up.

snuggs commented 7 years ago

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

icyc9 commented 7 years ago

Awesome. Will keep my eyes on this.

snuggs commented 6 years ago

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

snuggs commented 6 years ago

@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.

https://github.com/whatwg/html/issues/3402

snuggs commented 6 years ago

https://github.com/w3c/web-platform-tests/pull/9175 https://github.com/w3c/web-platform-tests/pull/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.

tmornini commented 6 years ago

@snuggs 👍

snuggs commented 5 years ago

@brandondees @tmornini @RobertChristopher @btakita @rianby64 TL;DR; Of what's on the platform spec horizon from TPAC meeting in TOKYO. #CustomElements2020

IMHO scoped encapsulation registries seems interesting.

https://docs.google.com/document/d/1HP4f-vYZ29uUlHDqxHdftoAFBnhQZ-UFnks3m5bRfA4/edit