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

@trusktr, I haven't yet wrapped my brain around the scoped registry solution, and consequently can't foresee what impact it will have on namespacing.  I'm waiting for the dust to settle.  But my instinct tells me it isn't going to solve every problem under the sun.  For example, I still think that we will want to *reduce* the need for complex and confusing mappings, so that  developers will still want to  *strive* to "namespace" their attributes based somewhat on their package name, document their libraries names based on this "canonical" naming, and that we will want to utilize scoped registries to rename things off of their canonical defaults,  only when absolutely necessary, due to inevitable  name collisions due to the limitations of relying on public npm packages exclusively for claiming "ownership" of a string. 

If anyone's understanding is different, I would love to get a response if anything I said above is inaccurate, because I'm only guessing, and it is something I feel like I should understand better to be attempting to add my voice to this proposal space. 

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

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