This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26485 - getWindowHandle does not define which context to operate on
Summary: getWindowHandle does not define which context to operate on
Status: RESOLVED FIXED
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency tree / graph
 
Reported: 2014-07-31 16:57 UTC by Andreas Tolfsen
Modified: 2015-10-26 03:51 UTC (History)
2 users (show)

See Also:

Attachments

Description Andreas Tolfsen 2014-07-31 16:57:28 UTC 
getWindowHandle does not define which browsing context it operates on.  It should say that it operates on the default content.
Comment 1 David Burns :automatedtester 2014-07-31 19:37:22 UTC 
Currently the prose says "The "getWindowHandle" command can be used to obtain the window handle for the window that commands are currently acting upon."

we can't use default content because we need to discuss something more than the current document, we need to be able to switch between different default contents in different browser tabs||windows

What would you prefer the prose to say in that regard?
Comment 2 David Burns :automatedtester 2015-10-26 03:51:58 UTC 
this is now fixed