New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 6 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 16
Cc:



Sign in to add a comment
link

Issue 1989: Document where WebDriver commands do a browser context check and when they do not

Reported by kereliuk@chromium.org, Sep 8 2017 Project Member

Issue description

Many webdriver commands don't implement the following step:

If the current top-level browsing context is no longer open, return error with error code no such window.

This step is present in many commands specified by the spec such as: https://w3c.github.io/webdriver/webdriver-spec.html#get-window-handle
 

Comment 2 by kereliuk@chromium.org, Jul 26 2018

Project Member
Owner: ----
Status: Untriaged (was: Unconfirmed)
Summary: Document where WebDriver commands do a browser context check and when they do not (was: Many WebDriver Commands don't implement a browser context check)

Comment 3 by johnchen@chromium.org, Aug 1

Project Member
Labels: StandardsCompliance Pri-2
Status: Available (was: Untriaged)

Comment 4 by johnchen@chromium.org, Aug 16

Project Member
Cc: kereliuk@chromium.org crouleau@chromium.org
Status: WontFix (was: Available)
ChromeDriver is already working correctly in this area. All commands that require a top-level browsing context (i.e., a window or a tab) uses ExecuteWindowCommand function (https://cs.chromium.org/chromium/src/chrome/test/chromedriver/window_commands.cc?type=cs&q=ExecuteWindowCommand) to retrieve the WebView object associated with the current browsing context. This function calls web_view->ConnectIfNecessary, which would notice that the window is already disconnected, and try to re-connect. The re-connect would fail, and a no such window would be returned.

Sign in to add a comment