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

Workaround for selenium webdriver does not work; the workaround gets triggered too late. NodeJS test code:

```js
var your_chrome_path = "/usr/bin/google-chrome-unstable";
var webdriver = require('selenium-webdriver'), chrome = require('selenium-webdriver/chrome');
var driver = new webdriver.Builder().
             forBrowser("chrome").
             setChromeOptions((new chrome.Options())
                              .setChromeBinaryPath(your_chrome_path)
                              .addArguments("enable-blink-features=ShadowDOMV1"))
var driverInstance = driver.build();
driverInstance.get("http://jsbin.com/xabazejuqe");
driverInstance.executeScript(function(){
  var origattachshadow = Element.prototype.attachShadow;
  Element.prototype.attachShadow = function(options){
    options.mode = "open";
    return origattachshadow.apply(this,options);
  }
});
```

Result: "This is some test text" is still inside a closed shadow DOM.

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