- From: Sasha Firsov <notifications@github.com>
- Date: Wed, 28 Sep 2022 23:21:42 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <WICG/webcomponents/issues/971/1261819641@github.com>
@codehangen , I like the idea but it has to be extended in order to be useful as connecting external resource with local content. If you along with URL would provide the local component **name(s) mapping** to declared name(s) in external HTML, that would be even more useful. Similar to import maps or JS import with mapping external export to local import. Now about link which would define the custom element(s). For JS, there is no need to import as there is a script tag for that. If link points to HTML, it would have define CE as Declarative Custom Element or HTML with JS for custom element definitions. If you want to load HTML with JS, you need to count on current resurrection of HTML include proposal. Whether the HTML would have the web component(s) registration or just some JS, is irrelevant to web components themselves. HTML without JS could define CE as Declarative Custom Element. The proposal is not yet shaped. So your proposal has a dependency on this standard to be. Or you had in mind different way of declaring CE? There is a row of alternative proposals of light version of CE : have a DSD `<template src="my-template.html">` as inline custom element substitution. or DCE `<element template="my-template.html" name="my-component">`. For both JS use protocol is in baking. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/971#issuecomment-1261819641 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/971/1261819641@github.com>
Received on Thursday, 29 September 2022 06:21:56 UTC