summaryrefslogtreecommitdiffstats
path: root/chromeos
diff options
context:
space:
mode:
authorpkotwicz@chromium.org <pkotwicz@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-11-26 01:45:15 +0000
committerpkotwicz@chromium.org <pkotwicz@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-11-26 01:45:15 +0000
commit21b59ff1510502381ad0892815424ce8b96497f8 (patch)
treea1f1f14e4bcbaf344e58bdcaad2239d003912ce5 /chromeos
parentb33a77161456fd6599b0975ea20951039ee0526c (diff)
downloadchromium_src-21b59ff1510502381ad0892815424ce8b96497f8.zip
chromium_src-21b59ff1510502381ad0892815424ce8b96497f8.tar.gz
chromium_src-21b59ff1510502381ad0892815424ce8b96497f8.tar.bz2
Currently, we do not cache the type of fullscreen that an app is in. When we relaunch an app which was fullscreen when the user closed the app (e.g. by pressing Ctrl+Shift+W), we relaunch it with the FULLSCREEN_TYPE_WINDOW_API fullscreen type. It is jarring when an app which was previously in immersive fullscreen is relaunched with the FULLSCREEN_TYPE_WINDOW_API type. Because immersive fullscreen for apps is still experimental, relaunch apps which were in immersive fullscreen when they were closed in maximized mode.
BUG=323061 TEST=Manual, see bug Review URL: https://codereview.chromium.org/84903004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@237225 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chromeos')
0 files changed, 0 insertions, 0 deletions