mirror of
https://github.com/encounter/engine.git
synced 2026-03-30 11:09:55 -07:00
Chris Bracken
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.