UserAgent: Mozilla/5.0 (X11; CrOS x86_64 8743.11.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.13 Safari/537.36
Platform: 8743.11.0 (Official Build) dev-channel cyan

Steps to reproduce the problem:
1. Install an Android application on ChromeOS via the dev channel
2. Launch the app
3. Check the display area available to your application - on an Acer R11 your window is only 568 pixels heigh

What is the expected behavior?
In Landscape mode, Android apps are put in a 960x600 pixel box.  600 pixels of screen height is relatively little.  When trying to run Windows apps via Wine, the entire 600 pixels is something of an absolute floor (some legacy Windows apps really expect at least an 800x600 display).  Unfortunately, under ChromeOS the usable space is only 568 pixels high because the top bar (which includes the "back" button and some resize tools) appears to take up 38 pixels.  

What went wrong?
I would hope the resizing toolbar would appear outside of the Android application's "box" when running under ChromeOS, or at least that more screen real estate would be available.  My app in particular causes ChromeOS to print a warning telling me it may not work well in fullscreen mode when I attempt to make it fullscreen, and when I launch it a second time after going fullscreen I am in Landscape mode again instead of fullscreen.  This makes the screen size limitation worse because the user has no way to work around it.  More user control over the screen size - or just more space - would be helpful.

Did this work before? N/A 

Chrome version: 54.0.2840.13  Channel: dev
OS Version: 8743.11.0
Flash Version: Shockwave Flash 23.0 r0