After the first tap the status bars come back.
Old code:
https://github.com/flutter/engine/blob/fcc26eeff8a706a4e876fec8168110f38f19b848/sky/services/activity/src/org/domokit/activity/ActivityImpl.java#L48
New code:
https://github.com/flutter/engine/blob/master/sky/services/platform/src/org/domokit/platform/SystemChromeImpl.java#L85
@jason-simmons says this is that the old code used to use SYSTEM_UI_FLAG_IMMERSIVE, which the new API doesn't really have a way to express.
I believe flutter/game is the only client of this API. So we probably should just fix it to suit flutter/game's needs for now.
It's also possible with the hello_services model that we can get out of the business of providing this abstraction (backed into the engine) entirely. FYI @tvolkert @abarth
After the first tap the status bars come back.
Old code:
https://github.com/flutter/engine/blob/fcc26eeff8a706a4e876fec8168110f38f19b848/sky/services/activity/src/org/domokit/activity/ActivityImpl.java#L48
New code:
https://github.com/flutter/engine/blob/master/sky/services/platform/src/org/domokit/platform/SystemChromeImpl.java#L85
@jason-simmons says this is that the old code used to use SYSTEM_UI_FLAG_IMMERSIVE, which the new API doesn't really have a way to express.
I believe flutter/game is the only client of this API. So we probably should just fix it to suit flutter/game's needs for now.
It's also possible with the hello_services model that we can get out of the business of providing this abstraction (backed into the engine) entirely. FYI @tvolkert @abarth