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

> Well I disagree. Have you asked the writers and users of that polyfill what they think? Their opinion matters much more than yours does.
the point here is, he's hardly alone...

This question have already been solved and it's again and again showing up by people, who think, they should have full control over 3rd party component. This is what it boils down to, the control... usecases (polyfills, keyboard shortcuts) are just examples of that. The point is it's always the author, who should have full control. By law and by tradition. If he/she chooses to release under public licence and /open/ mode, it's his/her call, if he chooses to release it under "do not touch the internals" and /closed/ mode, it's again his/her call. Page author must respect this choice, the choice he/she has is whether to use it, or not. The simple fact, that someone wants to poke inside component actually means nothing, regardless of how "good" reason they thing they have.
I am not saying, that license and open/closed are the same (licence can allow source code changes), I'm pointing out, that the choice, of both, is component's author in the first place, not anyone else.

there is a lot of "I do not agree here", the fact is, that while the need for /closed/ was agreed by majority, the need for total DOM control was not. This was never search for 100% agreement. There were always arguments about control/visibility. The component developers choice may mean very little to you, but it means very much for majority. The need of private states outweighs the fact, that some code will not work as originally intended.  

-- 
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-303236983