Re: [WICG/webcomponents] Exploration: HTML Module Imports and Exports (Issue #1059)

> and problems with name scope negotiation and recognizing by develloper

what problems, exactly?

The reason we should separate importing a thing from registering a custom element is that they will necessarily be different namespaces. From an HTML module we could import a DOM node, say a template or a reference to a custom element, and we need a way to refer to those as well as potentially register custom elements. If the import statement registers elements, it'll need two features - one for importing an identifier, another for registering custom elements. This is too coupled. We'd still need a way to register elements by HTML reference that aren't from an import - like a local definition.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1059#issuecomment-2103794326
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1059/2103794326@github.com>