Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902)

Could someone elaborate on the need to separate `AttributePart` and `ChildNodePart`?
From API interface and implementation I could not come up with any difference. Like none. 
If that is true, why we need separate interfaces? 

From "evolutionary architecture/design" prospective at this stage better to keep minimal/common interface and only when it appears to be needed, extend. No need so far? Drop it.

Also if/when `ATTRIBUTE` node would become declaratively available, the `PART` would be candidate for declarative definition as well. It would be same as within `SPAN` as within `ATTRIBUTE`.  

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

Message ID: <WICG/webcomponents/issues/902/1212666707@github.com>