Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049)

Few comments:

1. what are the benefits of using a whitespace-delimited multi-value string vs individual configurations? I don't see the ergonomics benefits, but I suspect it is not about ergonomics.
2. I don't think `encapsulate-ids` is possible, those IDs are defined by doc/fragment.
3. `encapsulate-events` is a little bit more subtle, and I'm not sure what's the issue with mode=open and events? if the shadow is open, you can still get to the individual elements by using the event path.
4. What does `none` means? you said lightdom with slots, but that's not possible as far as I can tell, the slotting mechanism only works if you have composed docs/fragments (essentially a shadow).
5. I'm also worry about the combinatorial aspect of this proposal, and the overlapping of the options, e.g.: "closed encapsulate-styles", what does that mean? closed has encapsulated styles, how can you make closed to not encapsulate styles?

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

Message ID: <WICG/webcomponents/issues/1049/1944142915@github.com>