-
Notifications
You must be signed in to change notification settings - Fork 61
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
Regular space characters are being stripped from text input #29
Comments
## [1.5.1](https://github.com/donotebase/quasar-tiptap/compare/@1.5.0...@1.5.1) (2020-08-22) ### Bug Fixes * **prosemirror-model:** multiple versions of prosemirror-model, fixed [#29](#29) ([a293fd1](a293fd1))
🎉 This issue has been resolved in version 1.5.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I don't believe this release actually has done it; the commit shows you added a new package and changed the
If |
Just realized that you replay after I closed this issue. |
## [1.5.1](https://github.com/donotebase/quasar-tiptap/compare/@1.5.0...@1.5.1) (2020-08-22) ### Bug Fixes * **prosemirror-model:** multiple versions of prosemirror-model, fixed [#29](donotebase/quasar-tiptap#29) ([a293fd1](donotebase/quasar-tiptap@a293fd1))
Tested using quasar-tiptap 1.4.4 (tiptap 1.27.1/tiptap-extensions 1.29.1) and then 1.5.0 (tiptap 1.29.6/tiptap-extensions 1.32.5). Discovered as a bug that was only replicable on Firefox, but exists due to a difference in how Chrome and Firefox handle spacebar input. Chrome will input a non-breaking space, but Firefox will input a regular space character.
At the end of a string (your current input), any regular space characters that exist will be stripped as the next character is typed. When trying to paste a single space character at the end of a line, it will not commit in either browser. This behaviour is also replicable in the demo page you provide.
The text was updated successfully, but these errors were encountered: