> The unfortunate bit there is the sensitivity to whitespace. I wonder if, similar to assignedNodes() vs assignedElement(), if we'd want two attributes so that if you only want to slot elements it's not sensitive to whitespace. My impression had been that declarative shadow’s use cases were tied up with some notion of producing/taking a “snapshot” which would likely not be maintainable without some kind of generative tooling (e.g. build tools if static or runtime libraries that don’t permit naive string concatenation if dynamic SSR). Since the concern expressed here seems to regard ergonomics, it made me wonder if there are additional motivating use cases where authors would be writing declarative shadows directly? (Idea seems fine to me, just trying to get a sense of how much this is meant to be an “author feature” vs (metaphorically) “html bytecode”). -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/967#issuecomment-1264336639 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/967/1264336639@github.com>
Received on Saturday, 1 October 2022 11:34:21 UTC