-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Windows: PageUp/PageDown collapses selection only #6811
Comments
@redmunds This is by design in CM. The first key stroke deselects the selection and navigation keys take effect only if there is no selection. You can see this behavior with Down/Up arrow keys as well, not just with PageUp/PageDown. On Mac the equivalent keys for PageUp/PageDown are fn-Up/Down arrow keys on laptop keyboard. |
@RaymondLim Was there an announcement explaining why this was recently changed? I've never noticed this behavior in any other editor. |
@redmunds No announcement that I'm aware of. I reviewed all of the changes in CM and Marijn put a note regarding his decision in either one of the commits or the issues that he fixed. I'll put a link here if I can easily find it again. Found it! codemirror/codemirror5#2042 |
@RaymondLim It's not something I ever hit personally, but this does seem odd to me -- it's not the behavior in Sublime, WebStorm, Notepad++, or Notepad (or even Word, for that matter). Are there Mac editors that behave this way? |
@redmunds and @peterflynn I totally agree with you that it's odd. But Marijn's codemirror/codemirror5#2042 (comment) claims that some do. |
It sounds like he's saying that only (some) Linux editors do -- not any on any other platform. That's not particularly helpful for us given that ~90% of our users aren't on Linux... |
Medium priority to @RaymondLim. I think we should push back on this change in CodeMirror - if it's literally the case that no other popular Windows or Mac editor works this way, we shouldn't change it just because some Linux editors do. Raymond, could you file a bug in CodeMirror, and maybe double-check a few popular editors in Mac and Win to back up our argument? |
This was introduced with CodeMIrror update for Sprint 36: #6268
Recipe:
Result:
Text is deselected. Cursor is placed after text that was selected. Editor is not scrolled.
Expected:
Editor is scrolled in addition to Results above
Workaround
Hit PageDown again.
The text was updated successfully, but these errors were encountered: