Re: [w3c/webcomponents] Generic programs can't reliably use/manipulate documents via the DOM (#640)

@dylanb @mrmr1993 I'm a webcomponent author (and sometimes a polyfill author) and the biggest advantage of using a closed shadow tree, for me, is knowing that I can make internal changes to my component without compromising its integrity in the wild.

Let's say, for instance, I release my amazing component, which is self hosted on my domain at path `/components/Amazing/1/Amazing.js`. Any web page author can use it by referencing this script.  Now, let's say that there's an edge case bug which can be easily fixed by changing the internal DOM in my component in some way.  If my tree is closed and I want to make this change, I can do so transparently by updating the script at its current URL.  If it's open and I want to make this change, I have to concern myself with how this may affect sites using the component and possibly make a separate, opt-in release, which will leave instances of the buggy version out in the wild on 3rd-party websites.

This is not me "telling kids to get off my lawn". This is me having peace of mind and not painting myself into a corner. This is where you can draw a parallel with UA-defined components. By keeping their internal tree hidden, they don't need to worry about breaking things when they change that internal tree.  You both indicated that a UA should be allowed this privilege, but a component author should not, which I find extremely puzzling!

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