Currently Flutter always listens to keyboard events assuming it owns the page. That should not be the case in multi-view state (not even in non-full-page single view case).

It's not yet clear what exactly needs to be done here. If we shut off keyboard events at the engine level, that could be limiting for some use-cases. For example, multi-view may be used for reasons other than add-to-app deployments, and the app may still want to handle keyboard globally. At the framework-level, we could be aware of when and which view is currently focused and only listen to keyboard events there while still giving the developer the option to handle keyboard globally. But before fixing keyboard we need to introduce focusability at the FlutterView level.

See also: #137344