- From: <bugzilla@jessica.w3.org>
- Date: Fri, 16 Aug 2013 23:06:53 +0000
- To: public-browser-tools-testing@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22987 Bug ID: 22987 Summary: Proposal: Shadow DOM support in WebDriver Classification: Unclassified Product: Browser Test/Tools WG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: WebDriver Assignee: public-browser-tools-testing@w3.org Reporter: fisherii@google.com QA Contact: public-browser-tools-testing@w3.org CC: mike@w3.org The current proposal for dealing with Web Components and their corresponding Shadow DOMs in WebDriver treats them similarly to frames; at any point in time the WebDriver session is operating within a particular DOM, either the top-level DOM or one of the Shadow DOMs of a particular Web Component. However, this makes interacting with pages that use Web Components extremely taxing, as the current DOM will have to be switched on a regular basis, and it is unclear over what time frame an element id found within a particular DOM will be considered valid. Instead I propose that the WebDriver wire protocol be extended with commands to get the list of attached Shadow DOMs for an elements as opaques IDs and to support new element and elements commands that are scoped to a particular DOM. Additionally, element IDs from Shadow DOMs be completely accessible as long they are the corresponding element attached to the Shadow DOM and the Shadow DOM is attached to the page. For a more thorough description see: https://docs.google.com/document/d/1qP7Se3MDUac5P0V1Kfm2yaj3fFhBOFCyWyXLcsVwkTA/edit?usp=sharing -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 16 August 2013 23:06:54 UTC