[Bug 28591] New: [Shadow]: Figure out a good replacement for /deep/ in testing scenarios

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28591

            Bug ID: 28591
           Summary: [Shadow]: Figure out a good replacement for /deep/ in
                    testing scenarios
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: dglazkov@chromium.org
        QA Contact: public-webapps-bugzilla@w3.org
                CC: annevk@annevk.nl, esprehn@gmail.com, mike@w3.org,
                    public-webapps@w3.org
            Blocks: 14978

One thing that immediately popped up once we started talking about removing
shadow-piercing combinators is that WebDriver-based tests are frequently
interested in reaching into shadow trees to grab a specific element to test:

https://code.google.com/p/chromium/codesearch#chromium/src/chrome/test/chromedriver/test/run_py_tests.py&sq=package:chromium&q=testShadowDom*&l=877

Web Driver actually has something currently that attempts to solve the problem:
http://www.w3.org/TR/webdriver/#switching-to-hosted-shadow-doms

However, the feedback I got from ChromeDriver folks is that it's way too
verbose and awkward to use for the most common case  (see above).

Maybe the solution is just specifying deepQuerySelector for WebDriver spec.
However, I want to make sure this is not just a one-off -- seems like this
could be needed in other contexts.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Friday, 1 May 2015 17:22:54 UTC