In text editor, fix behaviour of Home and End keys #836
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Usage and product changes
The behaviour of Home and End keys are now in line with most other text editors, moving to the start/end of the line (rather than the file) unless Ctrl (Cmd on MacOS) is additionally pressed.
Implementation
We had some confusing terminology in the
Command
class -MOVE_HOME
andMOVE_END
intuitively sounded like they should correspond to a keyboard's Home and End keys, but this resulted in incorrect behaviour. We've renamed them toMOVE_CONTENT_START
andMOVE_CONTENT_END
, and these are now correctly only triggered by Ctrl+Home and Ctrl+End respectively. Home and End take you to the start/end of a line. If Shift is additionally pressed in any case, trigger selection.