You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Soft breaks (shift + enter) are interpreted as hard breaks in Safari. They are detected correctly in Chrome. I tested the 'is-hotkey' library and 'shift+enter' works fine in Safari, so the bug must be somewhere in the Slate library. If no one has any ideas I can dig deeper and attempt to identify the issue.
Thanks for your reply, @frellica. It looks like you are correct, I wasn't looking deep enough. For whatever reason Safari has designated control+return for the insertLineBreak event type.
I may end up making a special rule for this, since our users expect shift + return to produce a line break, but it doesn't seem like something that Slate should need to account for.
Description
Soft breaks (shift + enter) are interpreted as hard breaks in Safari. They are detected correctly in Chrome. I tested the 'is-hotkey' library and 'shift+enter' works fine in Safari, so the bug must be somewhere in the Slate library. If no one has any ideas I can dig deeper and attempt to identify the issue.
Sandbox
https://codesandbox.io/s/slate-reproductions-forked-kxss7c?file=/index.tsx
Steps
To reproduce the behavior:
Expectation
Soft breaks should be detected in Safari as they are in Chrome.
Environment
Context
One of the requirements for my editor is that hard and soft breaks are treated differently (double space vs single space)
The text was updated successfully, but these errors were encountered: