Re: [webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)

I would like to apologize for my behavior earlier. That was clearly unwarranted. I'll reopen the issue to let someone else make a decision here.

In part the reason we have this feature is because we cannot seem to get agreement on shadow DOM without it. That is, at least vendor has stated that if we don't have this they won't play ball. 

I'm personally not swayed that this breaks testing, auditing, and Google Feedback anymore than cross-origin `<iframe>` does, or isolated components will, when we get there. I don't see why we should not leave it up to the developer to make the choice what kind of semantics they want. If you want to use those kind of tools, and not the browser developer tools, you cannot use this feature. Seems simple. If you have noticed that it becomes harder to upgrade your components when developers poke into them (as folks from Apple and Mozilla have repeatedly indicated has been a problem for them), you use this feature and opt out of testing/auditing in a straightforward manner (perhaps you support a different kind of switch for that).

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/354#issuecomment-178498561