Open mihailik opened 9 years ago
I'm getting contenteditable as default for the inputStyle
option on the android browser. Could you tell me the userAgent string your stock android browser produces?
Mozilla/5.0 (Linux; Android 4.4.4; UMI eMAX Build/KTU84P) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/33.0.0.0 Mobile Safari/537.36
That one's recognized as a mobile browser by CodeMirror, so barring some really weird thing happening, you should get "contenteditable"
as default input style.
From what I understand, this issue seems to be fixed. In any case, we are working on a rewrite (CodeMirror 6) that will address this and similar issues more thoroughly, and we are currently raising money for this work: See the announcement for more information about the rewrite and a demo.
Note that CodeMirror 6 is by no means stable or usable in production, yet. It is unlikely that we put much work into fixing this and similar problems for CodeMirror 5, though.
Standard Google on-screen keyboard on Android has no arrow keys, but some other keyboards do (we care for on-screen keyboards here).
When arrow keys like <-- or --> are pressed, the cursor moves, but the onscreen keyboard hides.
That happens on:
That does not happen on:
From other clues it looks like FireFox uses full 'contenteditable' inputStyle, whilst Android Browser seems to fall back onto 'textarea'.
Generally I've never had such problems in 'textarea', but ever since 'contenteditable' was introduced, the arrow keys have always been like that on Chrome.
Haven't got an iPhone, so cannot check Safari.