preview.app stuck on first page of PDF when in single page mode

What seems to be happening is that when we used to set Preview in "single page" as the default, a newly-opened document window was exactly the right size, and you could easily up/down arrow through the pages.

However, now it instead opens the document with the page ever-so-slightly too large for the window from side to side, so Preview switches into "Oh, you've zoomed in and you'd like to scroll around this ONE page", and so the arrow keys become the scrolling around that ONE page keys.

Except that since it's _vertically_ the right size, up/down doesn't scroll. Left/right arrows will, though.

If you slightly enlarge your window (or shrink the page) to include some space all around, you'll see the up and down keys work without the option/alt key.

And this behavior is still screwed up as of 2017-05-29 (OS 10.12.5). So <extremely bad swear word here>, Apple. You really haven't noticed this in your own work yet ?

Ricks56, I think you're exactly right about scrolling behavior. I bet you also have "Sys Prefs -> General -> Show scroll bars" set to "Automatic" or "Always". I found that switching the scrollbar display to "When scrolling" makes the problem go away. I think Preview isn't accounting for the width of the scrollbars when it opens a PDF. Since "When scrolling" is the default most people probably never encounter this. (Hiding the scrollbars except when actively scrolling is in itself a horrendous UI failure, but Apple seems to have really thrown away the good UI design handbook lately.)

Hold the Option/ALT key, then use the cursor UP or DOWN key.

It's not a workaround, it's the new Apple-designed behaviour. So, yes, everyone has the same experience.

If you have disabled continuous page mode, yes. My documentation is the app itself, specifically the Menu options provided in single page mode.

As for intuitiveness, that's why I use continuous page mode.

I'm having the same problem and I really do not think it's the way Apple designed it but rather a weird "in-between" glitch.

Why I say that is that after you "release" the document from the in-between mode, you can go ahead and use the up/down keys (without ALT) again. You can notice that it enters this in-between mode when you have a fully filled scroll bar on the right.

Really hope this gets solved soon... I tried trashing the Preview prefs but to no avail...

This is the most BIZARRE behavior I've seen. The applications are getting more and more annoying trying to hide or eliminate obvious behavior (and yes, obvious as this is the way it worked forever in all previous versions). Also: the first page that opens actually does NOT open in single page but in some "in between" mode. Lastly: why does not preview open in the last size of a windows that was used (e.g., using ALL top-bottom space available). VERY ANNOYING.

I agree with benjaminhoong. I believe this to be a bug. As further validation of this, the menu items Go->Up and Go->Down are available to click but do nothing when clicked until this "glitch" is unlocked after using Option-Arrow (or clicking on a different page in the thumbnails list.) If this was a purposeful (and baffling) "feature" from Apple those menu items would be disabled, I would imagine.

I will file a bug report with Apple and see what happens.

I cannot open any page on a PDF. I've just scanned documents and they won't open. I also checked scans I have on a flash drive and they are not visible either. This must be a Sierra 10.12.1 issue

Will do, dbarbi1. No activity on the bug report as of yet.

Your issue sounds like a different one than the one described in this thread, mberan. I have the same OS version you do and I don't have any problems opening PDFs. Try exporting a web page as a PDF using File->Export as PDF... in Safari. Then try to open it using Preview. You shouldn't have any issues.

Some activity on the bug report I opened: They requested that I attach a PDF file that is causing the issue. I told them that any multi-page PDF will do, but I attached one for them anyway. I was surprised when they didn't close my bug report as a duplicate (they usually are.) In any case, this is good news which means they've started to look into the issue.