Skip to content
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

iOS - Tapping return twice loses auto-capitalization #4004

Closed
chrisdeeming opened this issue Aug 10, 2020 · 3 comments
Closed

iOS - Tapping return twice loses auto-capitalization #4004

chrisdeeming opened this issue Aug 10, 2020 · 3 comments

Comments

@chrisdeeming
Copy link

chrisdeeming commented Aug 10, 2020

Expected behavior.

Each time return is tapped, auto-capitalization should be enabled.

Actual behavior.

If you tap return twice, auto-capitalization is lost. Pressing it a third time does not insert an extra new line break but restores auto-capitalization.

Steps to reproduce the problem.
  • Open this proof of concept on iOS: https://xenforo.com/bug-poc/froala/ios-enter.html
  • Ignore the title field
  • Tap into the Froala editor
  • Auto-capitalization is enabled
  • Enter the word "Test"
  • Tap return
  • A new line is created and auto-capitalization is enabled
  • Tap return again
  • A new line is created but auto-capitalization is disabled
  • Tap return again
  • No new line is created but auto-capitalization is re-enabled
Editor version.

v3.x

OS.

iOS (13 and 14 Beta)

Browser.

Any iOS

Recording.

https://www.youtube.com/watch?v=R5vpkB3wJbU

@chrisdeeming chrisdeeming changed the title iOS - Tapping enter twice loses auto-capitalization iOS - Tapping return twice loses auto-capitalization Aug 10, 2020
@antialiasis
Copy link

Any updates on this at all? It's quite annoying.

@chrisdeeming
Copy link
Author

This looks to have been fixed somewhere between v3.2.5 and v3.2.7.

Thank you. I do wish it hadn't taken so long but I'm pleased to see it resolved.

I've only tested in iOS 15 Beta so far so not sure if it also works in iOS 14 - trying to verify and will close this issue once I know.

@chrisdeeming
Copy link
Author

Can confirm after multiple users tested that this issue is now resolved.

Please keep it that way! This has been a painful period of time...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants