Bug 286383 - [navigation] Keys HOME, END, PAGE-UP, PAGE-DOWN move caret on Mac
Summary: [navigation] Keys HOME, END, PAGE-UP, PAGE-DOWN move caret on Mac
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.5   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 286486
Blocks:
  Show dependency tree
 
Reported: 2009-08-12 07:44 EDT by Stefan van den Oord CLA
Modified: 2019-09-06 15:33 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan van den Oord CLA 2009-08-12 07:44:46 EDT
Build ID: 20090619-0625

Steps To Reproduce:
1. Create a new untitled text file
2. Enter enough text in the file so that you have a scroll bar
3. Hit COMMAND ARROW-UP; text caret moves to start of document (= good)
4. Hit END; text caret moves to end of document (= wrong; caret should not move)

This is just an example. The bottom line is that COMMAND-UP and COMMAND-DOWN are supposed to move the caret on the Mac, but not HOME, END, PAGE-UP, and PAGE-DOWN.

In other words, these keys should be "scroll-only", as also mentioned in https://bugs.eclipse.org/bugs/show_bug.cgi?id=95950#c56.


More information:
The importance of the scroll-only functionality, is that on the Mac you can use these keys to quickly look elsewhere in your document. Since the caret is not moved, you can just hit an arrow key to return the scroll position to where you were editing. This behavior is described in the Apple HIG, and it is also the way Mac editors (such as BBEddit, Xcode; and in fact, any native text area on the Mac) work.
Comment 1 Markus Keller CLA 2009-08-13 04:41:28 EDT
This first has to be implemented in StyledText, see bug 286486.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:33:00 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.