I am working on an app which presents a form via a Dialog that uses a nested Navigator. When a TextFormField configured with KeyboardActions is triggered from within this form, the action bar displays at the bottom of the dialog and is locked within its bounds. It does not avoid the keyboard in this state and may be hidden behind the on-screen keyboard.
I believe what is happening is that the KeyboardActions are being overlayed onto the nested Navigator instead of the root Navigator.
I am working on an app which presents a form via a Dialog that uses a nested Navigator. When a TextFormField configured with KeyboardActions is triggered from within this form, the action bar displays at the bottom of the dialog and is locked within its bounds. It does not avoid the keyboard in this state and may be hidden behind the on-screen keyboard.
I believe what is happening is that the KeyboardActions are being overlayed onto the nested Navigator instead of the root Navigator.