I noticed that the textInput node (found in events/TextInput.js) that is used to
capture the text input in an editable text area, gets in the way when using
a plattform such as iOS (maybe also Android or other mobile OSes).
Since the textInput node constantly grabs the focus, the mobile operating systems
will accompany that by moving the view to center the (invisible) node and presenting
the keyboard which makes whole system unusable as soon as a couple text morphs are being
displayed in the scene. (any touch interaction will effectively cause the keyboard to focus)
I have found the only way to disable this behavior is by rendering the text node as display: none
when it is not in use. However that breaks the input mechanism for the text morphs.
I noticed that the textInput node (found in events/TextInput.js) that is used to capture the text input in an editable text area, gets in the way when using a plattform such as iOS (maybe also Android or other mobile OSes). Since the textInput node constantly grabs the focus, the mobile operating systems will accompany that by moving the view to center the (invisible) node and presenting the keyboard which makes whole system unusable as soon as a couple text morphs are being displayed in the scene. (any touch interaction will effectively cause the keyboard to focus)
I have found the only way to disable this behavior is by rendering the text node as display: none when it is not in use. However that breaks the input mechanism for the text morphs.
Any ideas on how to fix that?