Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)

@rniwa that is a very sensible approach indeed. I apologise if my comment was a bit naive.

Coming from a different angle, and arguing against the automated testing angle, wouldn't these tools have to update their code anyways to use `shadowRoot` even if the default was `open`? If the tools are just using normal DOM accessors and methods, they'd only be getting light DOM anyways. If they've got to update their code to use `shadowRoot` wouldn't they just add an override so that they could access closed shadow roots?

---
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/499#issuecomment-219596389

Received on Tuesday, 17 May 2016 01:32:40 UTC