-
Notifications
You must be signed in to change notification settings - Fork 329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editor issues with touch screens #715
Comments
Found mentions of this being an issue with React Native and causing issues with other projects. |
@ericscheid I just tried this on iOS (iphone) Safari and Firefox and do not have the same issue. Want to double check and see what happens now? I don't have iPad to be definitely sure. |
I know Codemirror has issues with mobile devices, specifically touch-interaction. Was this using touch or a separate keyboard? If touch, eventually when Codemirror 6 releases we can switch to that which solves a lot of the problems with touch screens. |
All I'm hearing is @calculuschild enthusiastic support for responsibe, mobile friendly redesign :) |
Tested on iPad IOS 12.5.4 with touch keybord — still occurs. |
Is this still occurring? |
Fixing this requires upgrading to Codemirror 6. |
Rather, this is not our bug at all, this is a codemirror bug, we have nothing to fix, and we already have a codemirror 6 issue. #3511 . Closing this. |
When editing on iOS (iPad, Safari) and I press the shift-key, it behaves as if it is locked on (despite being displayed as a normal shift-enabled state - i.e. not solid up-arrow with underbar).
That is, if I press this sequence of keys: shifttitle the editor will then contain
TITLE
, and notTitle
.Oh, the number of times I've written a title like
#HERE is THE magic OF the THING
(which is meant to be word-capped), or simplyHERE IS A SENTENCE WHERE I HAVE TYPED MUCH WORDS VERY CAPS BEFORE REALISING IS ALL CAPS ARGH
DELDELDELDELDELDELDELDELDELDELDELDELDELDELDELDELDELDELDELDELDEL.As noted above, the shift key has the appearance of one-tap-enabled, but behaves as if caps-locked. (Well, technically shift-locked, as Shift,! actually produces the
!
). If I had to guess, the page is consuming the keypress but not reflecting as having been typed, and thus the keyboard isn't releasing the shift-once state.This behaviour does not happen on MacOS in Chrome.
Does this happen on other mobile platforms?
I'd like to fix this behaviour as it is incredibly annoying, but I'm guessing it's more a case of react/javascript shenanigans than simply tweaking html5
autocapitalization
attribute value.The text was updated successfully, but these errors were encountered: