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

Issue 1993 link

Starred by 6 users

Issue metadata

Status: Fixed
Last visit > 30 days ago
Closed: Aug 31

Sign in to add a comment

Fullscreen Window command not spec compliant

Project Member Reported by, Sep 8 2017

Issue description

We do not return the correct payload in our current implementation.

According to spec, we must:
Return success with the JSON serialization of the current top-level browsing context’s window rect.

Currently we return null.
_driver.Manage().Window.FullScreen(); gives null reference exception (in Google Chrome with C#.Net).

It looks like the implementation is not proper.

Test execution result attached.

Result Message:	
System.NullReferenceException : Object reference not set to an instance of an object.
TearDown : System.NullReferenceException : Object reference not set to an instance of an object.

Project Member

Comment 2 by, Aug 3

Labels: StandardsCompliance
Project Member

Comment 3 by, Aug 22

Labels: Pri-2
Owner: ----
Project Member

Comment 4 by, Aug 31

Status: Started (was: Available)
Project Member

Comment 5 by, Aug 31

The following revision refers to this bug:

commit 0e97421916152cd3a56d75e254d29e8bff574180
Author: Cole Winstanley <>
Date: Fri Aug 31 18:58:44 2018

[ChromeDriver] Fix Maximize Window and Full Screen

Make the MaximizeWindow and FullScreen commands return the serialized
window rectangle to comply with W3C spec. Changed tests to tests this
behavior and to be more robust overall.

Bug:  chromedriver:1993 
Change-Id: Ie9656e14fc67b1f4541055a8f41e6fbc109cdd98
Reviewed-by: John Chen <>
Commit-Queue: Cole Winstanley <>
Cr-Commit-Position: refs/heads/master@{#588103}

Project Member

Comment 6 by, Aug 31

Labels: ChromeDriver-2.42
Status: Fixed (was: Started)

Sign in to add a comment