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
Selecting text, adding a mark, deselecting the text, then reselecting the text and trying to remove the mark does not seem to work. This is the case in both Slate 0.101.1 for my local development and I was able to recreate the issue with Slate's Rich Editor demo application.
double click to select a word with no marks (such as the 5th word "text").
Click on the "Bold" button to add a bold mark to the text.
Click on "Bold" button again to remove the mark
Observe that this behavior works as expected.
Click on "Bold" button again to add the mark once more.
Deselect the currently selected text
Double click to previously selected text to select it once more.
Click on "Bold" button again and observe that the mark is not removed this time.
Expectation
I'd expect for the mark to be removed since it's already applied to the selection.
Environment
Slate Rich Text Editor Demo Application (link above)
Additionally, Slate 0.101.1
Context
I'm still learning how Slate works but if someone can point me in the right direction regarding the internals here, I'd be happy to take a look at fixing this.
The text was updated successfully, but these errors were encountered:
Description
Selecting text, adding a mark, deselecting the text, then reselecting the text and trying to remove the mark does not seem to work. This is the case in both Slate 0.101.1 for my local development and I was able to recreate the issue with Slate's Rich Editor demo application.
Recording
Sandbox
You are able to reproduce this issue here as well: https://www.slatejs.org/examples/richtext
Steps
To reproduce the behavior:
Expectation
I'd expect for the mark to be removed since it's already applied to the selection.
Environment
Context
I'm still learning how Slate works but if someone can point me in the right direction regarding the internals here, I'd be happy to take a look at fixing this.
The text was updated successfully, but these errors were encountered: