- From: <bugzilla@jessica.w3.org>
- Date: Fri, 12 Jul 2013 14:32:02 +0000
- To: public-browser-tools-testing@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22653
Bug ID: 22653
Summary: Container visibility when children are visible, but
parent is hidden
Classification: Unclassified
Product: Browser Test/Tools WG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: WebDriver
Assignee: public-browser-tools-testing@w3.org
Reporter: andreastt@opera.com
QA Contact: public-browser-tools-testing@w3.org
CC: mike@w3.org
At the last W3C webdriver spec meeting we discussed the scenario where
you have an ancestral element hiding it's overflow, and a parent
element with two absolutely position child elements. The parent
element is not visible to the user, but as a container element for the
two visible child elements it can be considered interactable.
An example is a container element, such as a menu, located
off-viewport with its child elements in-view. From a user perspective
the menu is definitely visible, should webdriver also consider the
container visible?
See the following patch for an example:
https://github.com/w3c/web-platform-tests/commit/1c76adbcb5b718bbf8e4045a1598711fca89868d
The conclusion we reached at the meeting was it we would differentiate
between interactability and visibility. This has not yet been covered
in the specification.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 12 July 2013 14:32:04 UTC