Repository navigation
We should derive the system chrome ui overlay style from a layer #4630
Description
On iOS, using AppBarBehavior.scroll can cause the status bar overlay to go from being painted over a dark background to over a light one (or vice versa). Doing so without calling SystemChrome.setSystemUIOverlayStyle() will mean that the status bar will be hard to see in one of the app bar states (either visible or scrolled off).
e.g. in the Flutter Gallery's contacts demo:
App Bar visible
App Bar scrolled away
Activity
tvolkert commentedon Jun 20, 2016
/cc @HansMuller @Hixie maybe we should have have the option of showing a shadow in the app bar space... this is what the Google Photos app does in the single-photo page.
HansMuller commentedon Jun 20, 2016
The contacts demo already adds a shadow. The shadow doesn't help in this case because it's being added to the flexibleSpaceBar which fades out when the app bar get smaller than its toolbar.
We can't just make the shadow (the DecoratedBox with a gradient child, see contacts_demo.dart) the AppBar's parent because the Scaffold expects it's appBar to be an AppBar so that it can change its elevation and etc.
We could make the AppBar render the shadow itself with a flag for turning that on and off. Not super fluttery but probably the simplest tack.
Hixie commentedon Jun 20, 2016
This only matters on iOS, right?
Hixie commentedon Jun 20, 2016
(#4430 will make adding the shade effect trivial.)
tvolkert commentedon Jun 20, 2016
Yeah it only matters on iOS
16 remaining items
tvolkert commentedon Jun 6, 2018
@jonahwilliams any update on this?
jonahwilliams commentedon Jun 6, 2018
@tvolkert Took a break to work on android/buildroot issues but I'm back to working on it this week.
mehmetf commentedon Jun 20, 2018
@jonahwilliams Please give an update. This is actually a blocker for mulligan.
jonahwilliams commentedon Jun 20, 2018
PR is done waiting for LGTM and Green to land
jonahwilliams commentedon Jun 25, 2018
Fixed by #17672
github-actions commentedon Sep 2, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.