-
Notifications
You must be signed in to change notification settings - Fork 29.2k
[Framework] Support for Android Fullscreen Modes #81303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Any update on this PR? |
Yes! Thanks @Kotlinovsky! I've been away for a bit, but expect to push updates by tomorrow. :D |
@goderbauer, I think this is ready for another look, I am just curious about what you think of the callback. I put it in the ServicesBinding.. which I think is ok? Wanted to know what you think before I fix up all the documentation and add the last few tests here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Little nits here and there, but looks good to me!
Any updates with this PR? |
Engine changes have landed, just waiting on the engine roll and this should be good to go! :) |
Waiting a bit further for the engine change to roll to dev, there are some internal customers that are affected by the lower level java changes. Working on migrating them now. |
Update: Still waiting on the roll. 🙂 🤞 |
The engine change is being reverted, so this is on hold again. |
flutter/engine#27018 is the updated engine change |
Updates? |
The cirrus customer shard here is experiencing merge conflicts, which is odd. I am going to revert the dart fixes (which are causing the conflicts) and see if it resolves the failure. I can add them back after or in a follow up change. |
That did not seem to make a difference, putting them back. |
Hallelujah. Holy **** I have been waiting so long for this to be fixed. Thank you. Phew. |
What flutter version we could expect for this fix to be shipped? |
Thank you! Equally important: Since this issue has been around for ages, and many people have done workarounds, would be great if there's documentation explaining the canonical way of handling this. Not to mention, in Android, users can change the navigation mode to "classic" or "gesture" anytime. |
This adds support for varying Android fullscreen modes, which affect the visibility of system ui overlays like the status and bottom navigation bars.
For the first three modes, there is also a new callback exposed so developers can be notified when the system overlays change, and what state they are in.
Finally, this change also updates the SystemChromeStyle, adding the ability to override the translucent scrim that is automatically added in Android to ensure proper contrast with system overlays.
Engine side: flutter/engine#25785
Related Issues:
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.