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

I disagree about decoupling of import and registering in the scope. It creates extra unused namespace and problems with name scope negotiation and recognizing by develloper.

All languages (try to find otherwise) including JS have import and mapping to name in the same statement.
 
The following convention would fix this irrationality:
```html
<define id="element-two">
    <registry>
        <script src="./element-one.html" type="html" imports="element-one"></script>
        <define tagname="el-one" from="element-one">
    </registry>
    <template>
        <el-one></el-one>
    </template>
</define>
```
Not in favor of tag names though. It overlaps with standard ones (XSLT) wthout inheriting its semantics and syntax. 

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

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