Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)

@LeaVerou 

> Hm. I need to understand the use cases more where scoping comes into play with attributes.

Unless I'm missing something, the basic scoping problem is the same for both custom elements and custom attributes.

The issue with custom elements is basically this: `my-element-a` might import and depend on `fancy-list` and `my-element-b` might import and depend on *a different* `fancy-list`. Custom elements are designed, in general, to have their details encapsulated but the dependence on `fancy-list` leaks since its existence is global.

The same issue could occur with `my-element-a` importing and depending on `HTMLInputElement.attributeRegistry.define("ac-list", ListAttribute);` and `my-element-b` importing and depending on a different `ac-list` attribute.



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

Message ID: <WICG/webcomponents/issues/1029/1719932054@github.com>