To Test:
- launch the demo app from scratch
- Tap on a RichText block: Welcome to Gutenberg
- observe the cursor appears, the block gets selected, the keyboard appears and the editor toolbar reflects the Heading style
- now tap into Hello World
- observe the cursor appears there, the block gets selected, the editor toolbar reflects the text style, but the keyboard gets hidden.

What should happen?
- the keyboard should not go away when tapping on an editable component.
Observe that the contrary (jumping from PlainText to RichText) does not happen:
- launch the demo app from scratch
- tap on a PlainText based component, for example Code block
- observe the keyboard appears, cursor blinks
- now tap on a RichText component
- observe the keyboard is not dismissed.
Where
This is observable both on the emulator and on a real device (Google Pixel 8.1)