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

@hayatoito request to revive? Google web fundamentals advice [notes the feature as 'should avoid'](https://developers.google.com/web/fundamentals/getting-started/primers/shadowdom#closed), stating much the same arguments we've been making all along.

To clarify, concrete proposal is to depreciate the `mode` key of the first argument of `attachShadow`, making  `attachShadow({"mode": "closed"});` fall back to the current behaviour of `attachShadow({"mode": "open"});`.

I'll also note that there is still no automation, accessibility or extension spec/implementation (that I can find) with a workaround for inspecting closed shadow DOMs. I still personally consider these the bare minimum interfaces that should have this privileged(/not suffer diminished?) access.

-- 
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/354#issuecomment-299681485