Opt-<Up Arrow> and Opt-<Down Arrow> for page up/page down Cmd-<Up Arrow> and Cmd-<Down Arrow> for beginning/end of the document

-> brade, mac keyboard

Reporter, can you provide some documentation (from Apple, perhaps) on those standards? I presume they're intended to be available when the user's keyboard lacks the Home/End/Page Up/Page Down key group.

Please see the URL I added to this bug. The relevant portion is Table 8-1. This reference is clear on the Cmd-Up/Cmd-Down combos, but a little more ambiguous about Opt-Up/Opt-Down. However, almost every display application (web browsers, Acrobat, etc) and most text editors (BBEdit, etc) substitute "page" for "paragraph" in this guideline. Since there isn't an insertion point on a web page (excluding textareas, which are a totally different topic) I believe this is a perfectly sound assumption to make. And every other web browser I tried (OmniWeb, IE, iCab) agreed with me. Yes, this is useful for those who don't have page-up/page-down and home/end keys. I also happen to use it exclusively, even though I have Page-Up/Page-Down keys on my MS Natural keyboard. For some reason I just find it faster. *shrugs* "Muscle memory" and all that.

Nick, thanks very much. That's exactly what was needed here. However, those keys are pertaining to insertion point navigation, not page scrolling. So, this is applicable to Editor (Composer and mail message editing). Moving to "Browser/Editor: Composer" and marking as a bug 73812 blocker. Though it may be convenient to interpret that Apple document in terms of page navigation, it is quite clear in referring to the insertion point, which is neither displayed nor available in any sense of the word in a Navigator window. It is not wise for Mozilla to loosely interpret genuine UI guidelines. In that context, almost all of the key sequences specified in Table 8-1 work in Composer, except Option-UpArrow and Option-DownArrow. Those need to be implemented. Likewise, almost all of the key combinations in Table 8-2 are implemented, except for Shift-Option-UpArrow and Shift-Option-DownArrow, which need to be implemented. (These were tested using Mac/2001091311 (0.9.4)). All this being said, if you wish to file an RFE requesting additional keyboard navigation functionality, feel free to do so. The document you reference simply doesn't define it.

Modifying summary slightly to more accurately reflect the report.

Is this bug OSX-specific? It works as I expect on OS9 with a Mac debug build from last week. The only problem I see is that the caret doesn't move with some commands (see bug #4302 but ignore the windows-keybinding of "PageUp/PageDown" since the Mac keybinding for this functionality is option-upArrow and option-downArrow). I think this is a duplicate of #4302 unless someone can clarify.

brade, the Option-UpArrow and Option-DownArrow key combinations aren't supposed to mimic PageUp and PageDown. To quote: Option?Up Arrow: To the beginning of the current paragraph, then to the beginning of the previous paragraph Option?Down Arrow: To the end of the current paragraph, then to the end of the next paragraph (not to the blank line after the paragraph, if there is one) Likewise, Shift?Option?Up Arrow: To the beginning of the current paragraph, then to the beginning of the next paragraph Shift?Option?Down Arrow: To the end of the current paragraph, then to the end of the next paragraph (include the blank line between paragraphs in cut, copy, and paste operations) I've changed the summary once again to be perfectly specific.

ok, this is currently Future then (and may well be a duplicate of another bug). There are no plans to implement functionality to detect "paragraphs". The best we can do right now is to scroll pages (instead of paragraphs) and insert caret at that location (bug #4302). This is the current functionality.

*** Bug 139702 has been marked as a duplicate of this bug. ***

-->mjudge

*** Bug 305347 has been marked as a duplicate of this bug. ***