Comment

Comment by akersten

With the disclaimer that I might be getting old, and I have done absolutely no research on my own about this whole shadow DOM thing: why would you go through all this trouble to "[provide] a way to scope CSS styles to a specific DOM subtree and isolate that subtree from the rest of the document."

Intuitively, I'm sure the whole Shadow DOM thing is way more powerful than that, but this is their 2nd-sentence headline example of what Shadow DOM "does."

Surely, there are reasons for all this complexity beyond stylesheet compartmentalization? Would I ever personally want to write the "raw" code to work with the Shadow DOM (not from the looks of it) unless I were a developer of some low-level framework that needs to be optimized to not manipulate the real DOM?

parent akersten 6 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton