Open Bug 1428814 Opened 6 years ago Updated 1 year ago

WebDriver:GetWindowHandle incorrectly checks selected window for content browser in content context

Categories

(Remote Protocol :: Marionette, enhancement, P3)

Version 3
enhancement

Tracking

(Not tracked)

People

(Reporter: ato, Unassigned)

Details

When the currently selected chrome window does not have a content browser, the Mn tests expect a no such window error to be thrown in content context when getting the window handle.

This seems like incorrect behaviour because WebDriver:GetWindowHandle is meant to work in the currently selected context: it doesn’t matter if the currently _selected_ window does not have a content browser for as long as the content browser in the current context does.
[Mass Change 2018-01-15] Moving bugs to backlog
Priority: -- → P3
Severity: normal → S3
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.