iOS Safari: Double-tapping the space bar doesn't insert a period
See original GitHub issueDo you want to request a feature or report a bug?
bug
What’s the current behavior?
Even when iOS’s ‘“.” Shortcut’ keyboard setting is enabled, double-tapping the spacebar in Slate doesn’t insert a period.
https://jsfiddle.net/rgrove/v0mkz2w0/4/
What’s the expected behavior?
When iOS’s ‘“.” Shortcut’ keyboard setting is enabled, double-tapping the spacebar should insert a period followed by a space, as it does in a <textarea>
or a native text field.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:23 (21 by maintainers)
Top Results From Across the Web
Stop the Period Automatically Typing in iOS | OSXDaily
Double tapping the spacebar on an iPhone or iPad inserts a period at the end of a sentence and starts another, a helpful...
Read more >How to Disable the Double Spacebar Auto Period in macOS
Open System Preferences; Access Keyboard Settings; Disable the macOS double-space period.
Read more >iPhone: Disable the "double-tap spacebar for ." shortcut?
One use-case I found: In a UISearchBar where you know the user is typing a series of words to be used as criteria....
Read more >How to Enable the Double Tap Period Shortcut on an iPhone
Slide the "." Shortcut button to the On position. Now you can quickly double-tap Space while typing to automatically insert a period followed...
Read more >iPhone 11 and iPad stopped inserting a period after double ...
You can edit this setting in „General“ -> „Keyboards“ -> “.“ Shortcut.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@rgrove I think augmenting the current usage would be a good start, unless replacing is the only way to achieve what we want. I’m open to either solution there.
As for preventing the browser from inserting text—I don’t think we actually have to do this. The current
onInput
handling assumes that the browser has already inserted text, for example this is how the current spellcheck-handling behavior works. We could either let all of the input through, and backport the changes to the internal model. Or we could just expand the cases that let the input through, to handle these iOS cases, if there’s a way to discern them. (Potentially by using theevent.inputType
flag.)It looks like this bug was introduced in #1088 with the removal of
isNative
(which also caused #1176). Please see #1176 for more discussion of this issue.