Add flag to enable immersive fullscreen for v2 apps

ash/ash_switches.h

Index: ash/ash_switches.h
diff --git a/ash/ash_switches.h b/ash/ash_switches.h
index 612083b347e48e297d060e64c628ff77246bd8f5..c2848e2b33b15f9c82487e458c82a1fecb12ae99 100644
--- a/ash/ash_switches.h
+++ b/ash/ash_switches.h
@@ -43,6 +43,7 @@ ASH_EXPORT extern const char kAshEnableAudioDeviceMenu[];
 ASH_EXPORT extern const char kAshEnableAdvancedGestures[];
 ASH_EXPORT extern const char kAshEnableAlternateFrameCaptionButtonStyle[];
 ASH_EXPORT extern const char kAshEnableBrightnessControl[];
+ASH_EXPORT extern const char kAshEnableAppImmersiveFullscreen[];

[oshima, 2013/11/08 23:25:32]

chrome/common/chrome_switches?

[pkotwicz, 2013/11/09 00:09:02]

I am keeping it here. In terms of precedent, --ash-enable-immersive-fullscreen
was also in ash_switches.h (See https://chromiumcodereview.appspot.com/14366004)

[oshima, 2013/11/09 01:11:18]

That flag shouldn't have been in ash first place IMO. Flag should be in the
component where the feature is toggled.

[pkotwicz, 2013/11/13 00:10:13]

We unfortunately need to keep the flag in ash. I will need to use it (from
CustomFrameViewAsh) in order to implement putting non-app windows like the task
manager into immersive fullscreen.
I plan on implementing this via a custom WindowStateDelegate if
|WindowState::delegate_| is non-NULL

I have renamed the flag to kAshEnableImmersiveFullscreenForAllWindows to make
its intent clearer

[oshima, 2013/11/13 07:21:36]

Ok.

 #if defined(OS_CHROMEOS)
 ASH_EXPORT extern const char kAshEnableFullMultiProfileMode[];
 #endif