New blog post:
3 Methods for Scoped Styles in Web Components That Work Everywhere
@zachleat I was thinking, what the hell is this webc thing? Browsers do this now? And then I realised what it is :) Maybe the pros and cons section should have “requires a build step” item and maybe a “requires 11ty” item? But that aside, this is neat and a really useful summary, thank you. I didn’t realise that the declarative shadow root stuff is pretty much usable now!
@sil Good feedback, thank you!
@zachleat I’d love to know more about the actual time difference to go from three starts to one in the performance section for DSD to CSSD. I get the star cost of requiring JS, but for such a trivial component, I’d say the difference would be negligible and for more complex components I’ve seen, with out numbers to share right now , CSSD be as fast or faster than DSD.
As in all things, the “it depends” is strong with this one, I know.
@zachleat It would also be cool to see if the duplication costs you‘ve listed are dev time or view time expenses. With a tool, like 11ty, you’re not quoted to duplicate that data yourself and with gzip/brotli the actual file size costs of that duplication seem to be mostly nullified?
I’m definitely pushing for shareable stylesheets in this area, the new @sheets proposal should help here, but there may still one piece of API missing if you want those @sheets to be in an inline <style> tag.
@westbrook I would really love an old fashioned blog-off on this one! I think there is plenty of nuance to be had here!