- From: John Jansen <John.Jansen@microsoft.com>
- Date: Tue, 2 Jun 2015 14:10:40 +0000
- To: David Burns <dburns@mozilla.com>
- CC: "public-browser-tools-testing@w3.org" <public-browser-tools-testing@w3.org>
> Fullscreen is not the same as maximised as some browsers ask permission when moving into fullscreen mode. We would need to be able to allow people to go fullscreen and not be
> blocked by the doorhanger. On some browsers (maybe just Firefox) there is a property that you can read to see if the UA is in fullscreen mode.
> As for maximised I can see doing this all within resize. If a user wants to go to maximised they would need to do something like in driver.maximise_window()
>
> ```
> def maximise_window(self):
> render_surface_dimensions = driver.execute_script("return {height: window.screen.availHeight, width: window.screen.availWidth}")
> driver.set_window_size(render_surface_dimensions[height], render_surface_dimensions[width])
> ```
>
> Instead of calling `driver.maximize_window()` and letting that send it over the wire. I don't mind either way really.
Thanks for explaining. I just misunderstood the difference in the spec. Now it makes sense. I think we should leave the spec with a Maximize function because it does make it easier for automation and everyone would expect it to exist. I think if "Fullscreen" gets fully described in the spec, it will make a lot more sense why they are different. I didn't realize you were really describing "F11". :-)
Received on Tuesday, 2 June 2015 14:11:09 UTC