e059cc0258
There are two different sets of view insets that applications may want to track in order to avoid unwanted interaction with system UI: 1. OS UI that effectively shrinks the Flutter view from a UX point of view: e.g., when the keyboard opens, it occludes the bottom of the screen and the view should be adjusted such that the bottom, for the purposes of scrolling is just above the keyboard. 2. OS UI that is overlaid over the application, but into which the application should draw. e.g., the Home indicator on the iPhone X typically appears near the bottom of the screen, overlaid over app content. Content should be rendered within this 'safe area' but apps should avoid requiring user interaction there. For example, list views may want to include some small amount of additional padding to ensure the last list item can scroll above this area. Since Flutter does not currently distinguish between these two cases, this patch disables the bottom safe area inset until API is added to support these separately.
Flutter Engine
Flutter is a new way to build high-performance, cross-platform mobile apps. Flutter is optimized for today's, and tomorrow's, mobile devices. We are focused on low-latency input and high frame rates on Android and iOS.
The Flutter Engine is the runtime environment for hosting Flutter applications. Most developers will interact with Flutter via the Flutter Framework and APIs, which run inside the engine.
Flutter is an early-stage open-source project. We are still adding features. However, you can build demos and examples today. We hope you try it out and send us feedback.
-
For information about using Flutter to build apps, please see the getting started guide.
-
For information about contributing to the Flutter framework, please see the main Flutter repository.
-
For information about contributing code to the engine itself, please see CONTRIBUTING.md.
Community
Join us in our Gitter chat room or join our mailing list, flutter-dev@googlegroups.com.