Currently Being ModeratedJul 21, 2011 4:11 PM (in response to DStewart)
I don't imagine you're going to find an easy fix for Page Up/Down, etc, but there is an easy fix for the scrolling issue. Scrolling is reversed in Mac OS X Lion to make it "feel more natural". You can change it back to the way it was by going into System Preferences, choosing Mouse, and then deselcting the checkbox at the top that says something along the line of "Use natural scrolling direction".
Currently Being ModeratedJul 21, 2011 4:15 PM (in response to DStewart)
Thank you for your help and answer.
And now, on to editorial:
Oh my God. So Apple has decided that if it can't be done (because it doesn't exist) on an iPhone screen, then it shouldn't be done on a desktop computer screen with a full keyboard?
Page Up and Page Down are not useless. And the iPhone is not a desktop computer. Its interface should not determine the interface of a desktop computer that is fully equipped with a fully capable keyboard and mouse.
Currently Being ModeratedJul 21, 2011 4:14 PM (in response to DStewart)
If you go into System Preferences / mouse, or System Preferences / Trackpad, then select Point & Click, uncheck 'Scroll Direction: Natural'. This will fix the reversed-scroll issue.
Currently Being ModeratedJul 21, 2011 4:18 PM (in response to DStewart)
Page Up/Down, Home and End all work for me in Safari as well as the Arrow keys. I have turned off Lions backward scroll feature and all seems to be working normally now.
Currently Being ModeratedJul 26, 2011 11:09 AM (in response to DStewart)
Keyboard commands for TOP and BOTTOM of page:
- COMMAND DOWNARROW takes you to bottom of page
- COMMAND UP ARROW takes you to top of page
Keyboard commands for PAGE UP and PAGE DOWN
- OPTION DOWNARROW takes you down a page
- OPTION UPARROW takes you up a page
Works here for me -- hope this helps.
Currently Being ModeratedJul 26, 2011 11:20 AM (in response to Michael Sidoric)
Michael, thanks, this all does work.
But what used to work for Page up and Page down were: Page Up and Page Down. These do work in Reader view, but not in the normal browser window.
Currently Being ModeratedJul 26, 2011 11:34 AM (in response to DStewart)
Understand – within Safari – the modifier is required.
Thanks for your patience, Lion is a bundle of discovery and new stuff, often in unlikely places. ;-)
Currently Being ModeratedJul 27, 2011 4:05 PM (in response to Michael Sidoric)
THANK YOU for these key commands to get around this stupid annoying problem. I've now created some Keyboard Maestro macros to execute those keystrokes when I press the Page Up, Home, etc. keys. Safari now works as expected, which is to say, like they do in every other app on my Mac and the free world.
Currently Being ModeratedAug 4, 2011 5:07 AM (in response to DStewart)
My navigation keys aren't working in Safari 5.1 either (either in Snow Loepard or Lion), but if I make a test user and run Safari under the brand new uncluttered by years of addons account, they all work as expected. I suspect there's some subtle incompatibility with an old Safari extension that I can't find that's capturing home/end/pgup/pgdown.
Currently Being ModeratedAug 4, 2011 5:26 AM (in response to pfriedel)
And having confirmation that I wasn't crazy was enough to make me search for what was going on. I had a custom key binding definition in ~/Library/LeyBindings/DefaultKeyBinding.dict that was interfering with Safari's keyboard handling. I removed it and now Safari page navigation works as I expected it to.
Currently Being ModeratedAug 4, 2011 7:21 AM (in response to pfriedel)
This is the correct answer. Thanks. I moved the DefaultKeyBinding.dict file to the desktop, restarted Safari, and it's fixed. Now to figure out what to do with that....
I want to mark your answer as correct, but can only see "Helpful Answer" available.
What this means is my original plaint was wrong--this is not some new Lion feature or change, but a bug of some kind in Safari 5.1 that allows a conflict with old keybindings.
Currently Being ModeratedAug 19, 2011 12:04 PM (in response to DStewart)
This is going to affect anyone who's edited their DefaultKeyBinding.dict (or used an app like KeyFixer) to make PageUp/PageDown/Home/End behave the way they do on Windows.
- PageUp/PageDown scroll up or down one page, but do not change where the cursor is.
- Home/End scroll to the beginning or end of the document, but do not change where the cursor is.
- PageUp/PageDown scroll up or down one page, and do change where the cursor is.
- Home/End move the cursor to the beginning or end of the current line.
OSX has event codes for all these. Normally the Mac uses the scrollPageUp: and scrollPageDown: events triggered by the page up/down keys. Many people (myself included) are more used to the Windows behavior and have changed the events triggered to pageUp: and pageDown: (note the lack of "scroll" at the beginning) which do it the Windows way.
Safari used to recognize both sets of events. Since there's no real concept of a cursor in Safari (unless you're in a text input field) the scrollPageUp: and pageUp: events were equivalent. Starting with 5.1 Safari ignores the Windows-like pageUp: and pageDown: events. If you've remapped your keys to the Windows style you can no longer use those keys in Safari.
Bug or feature? Normally I'd say bug, but there are so many other bad my-way-or-the-highway design decisions in Lion that I expect it was a conscious decision on someone's part to remove support for anything Windows-like.
Currently Being ModeratedJul 7, 2012 10:43 AM (in response to Michael Sidoric)
Thank you, you did help me. I was not able to find this simple info anywhere.
Currently Being ModeratedJan 30, 2013 11:58 AM (in response to Steve.Meida.King)
Fortunately, I was able to use BetterTouchTool to map PageUp/PageDown/Home/End to the corresponding option and command key sequences just for Safari. Works great.