Mash: Support Chrome App immersive mode
The client-side window frame/client layout code uses a per-window property (the pre-existing kTopViewInset) to layout the contents, rather than hardcoded values plus logic related to window state. This is necessary so that apps will be laid out appropriately in immersive mode when not fullscreened (i.e. maximized in tablet mode). Also, propagate some window properties across processes. Bug: 640365 Change-Id: I485920c242e1c98450d0868e078f534489525f7c Reviewed-on: https://chromium-review.googlesource.com/1195886Reviewed-by:Tom Sepez <tsepez@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#588894}
Showing
Please register or sign in to comment