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

Unable to copy/cut when only void inline node is selected #2124

Closed
uipoptart opened this issue Aug 24, 2018 · 3 comments · Fixed by #2198
Closed

Unable to copy/cut when only void inline node is selected #2124

uipoptart opened this issue Aug 24, 2018 · 3 comments · Fixed by #2198

Comments

@uipoptart
Copy link
Contributor

Do you want to request a feature or report a bug?

Bug

What's the current behavior?

  • Insert void inline node
  • Click on a void inline node it’s state to selected (in this case it gets a black outline)
  • Use the keyboard or dropdown menu to copy
  • Paste
  • The copied node is not actually copied to the clipboard. The same behavior happens with cut.

copy

Didn't include a fiddle as this happens in the current emoji example.
https://www.slatejs.org/#/emojis
Mac OS 10.13.6
Google Chrome 67.0.3396.99

Some background:
In our use case, the void node contains underlying data that customized by the user. Like the emoji, some of it is displayed by the inline for the user to see. This scenario makes just inserting another instead of copy/pasting much more time consuming.
copy

What's the expected behavior?

The inline node is copied (or cut) to the clipboard

@ianstormtaylor
Copy link
Owner

Due to the tangential discussion in #1744 I've rolled this back. We need to find a solution that solves this without breaking the existing behaviors.

@laobeijing0806
Copy link

I have the same issue here, any updates?

@ianstormtaylor
Copy link
Owner

I believe that this may be fixed by #3093, which has changed a lot of the logic in Slate and slate-react especially. I'm going to close this out, but as always, feel free to open a new issue if it persists for you. Thanks for understanding.

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

Successfully merging a pull request may close this issue.

3 participants