#DeclarativeWebApplication manifesto 1st draft created. It sounds too good and futuristic but some of it already covered by POC and parts of its stack are under #WICG review.

https://github.com/EPA-WG/dwa#readme

@w3c , @w3cdevs

#DeclarativeCustomElement parts moved to #WICG as proposal. The *Functionally complete declarative templating* comes first.

#webdev , vote it up in github👍
https://github.com/WICG/webcomponents/issues/997

#webcomponent tag names and the registry have been a broken concept from beginning as do not support the enterprise grade apps where on same page different versions of same component could co-exist. And to make it worse, same tags can be used by custom elements from different vendors.
The web components needs a concept of loader and scope. Where exported by lib tags would be loaded on demand utilizing importmaps for url resolution and mapped to local scope names.

#wicg

#webdev world get used to insulation, no side effects concept. #webcomponent and react just to name if few. Besides of IFRAME the html standard have not adopted much of such significant pattern yet. HTC has given a big promise but seems to be ahead of time by the century.
Now in web 3.0 world where apps from different vendor live on same page, the insulation and coordination become a desperate need.

In the scope of #DeclarativeWebApplication

#wicg proposals are coming

If you think the #HTML templating worth improvement, please take your vote or opinion on #wicg proposal

#webcomponents #customelements

https://discourse.wicg.io/t/proposal-fully-functional-declarative-template/6115

RT @MozillaZineFr@twitter.com

Navigateurs : la fin de l'user agent fait des victimes #NetMarketShare #WICG /@frsilicon #actu https://www.silicon.fr/navigateurs-user-agent-victimes-350449.html

Navigateurs : la fin de l'user agent fait des victimes #NetMarketShare #WICG /@frsilicon #actu https://www.silicon.fr/navigateurs-user-agent-victimes-350449.html