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

Ubuntu: CTRL + SHIFT + UP doesn't work as expected #2427

Closed
djordjeandrejevic opened this issue Oct 27, 2020 · 2 comments · Fixed by #2428
Closed

Ubuntu: CTRL + SHIFT + UP doesn't work as expected #2427

djordjeandrejevic opened this issue Oct 27, 2020 · 2 comments · Fixed by #2428
Assignees
Labels
bug Something isn't working
Milestone

Comments

@djordjeandrejevic
Copy link

djordjeandrejevic commented Oct 27, 2020

CTRL + SHIFT + UP keyboard combination doesn't work as expected in Simplenote 2.0.0 on Ubuntu.

Steps to reproduce

  1. Create a list
  2. Place mouse pointer somewhere on the last list item
  3. Press CTRL + SHIFT + UP multiple times

Expected

Standard highlighting as seen on the screenshot below (Windows 10).

Screenshot_63

Observed

Multiple pointer lines appeared.

2020-10-27_19-52

P.S. I haven't tested this with CTRL + SHIFT + DOWN combination, but I assume it's the same as with UP.

OS Version App Version
Ubuntu 18.04 LTS Simplenote 2.0.0
@djordjeandrejevic djordjeandrejevic added the bug Something isn't working label Oct 27, 2020
@codebykat
Copy link
Member

I can reproduce this on the Monaco playground.

#2428 disables those shortcuts, but it doesn't seem to restore the native selection behavior. I wonder if it's because there's not an underlying text area? We might not be able to fix it without a patch to Monaco (the upstream editor component).

@belcherj belcherj added this to the 2.2.0 milestone Nov 9, 2020
@codebykat
Copy link
Member

Will be fixed in 2.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants