Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 65851 Navigation in PDF based on page# in URL - nice to have feature
Starred by 25 users Reported by, Dec 8 2010 Back to list
Status: Verified
Closed: May 2011
NextAction: ----
OS: ----
Pri: 3
Type: Bug

  • Only users with Commit permission may comment.

Sign in to add a comment
Chrome Version       : 8.0.552.215
URLs (if applicable) :
Other browsers tested:
       IE 8/9: OK

What steps will reproduce the problem?
1. Open URL to PDF file with #page=nn

What is the expected result?
PDF is opened on the page by the parameter #page.

What happens instead?
PDF is opened on the first page.
Labels: -Area-Undefined Area-UI Feature-PDF
This works with Adobe's PDF Plug-In.
Comment 2 by, Jan 12 2011
Labels: -Pri-2 Pri-3
Status: Untriaged
Summary: Navigation in PDF based on page# in URL - nice to have feature (was: NULL)
Comment 3 by, Apr 4 2011
Another parameters in RFC 3778 chapter 3:
Status: Started
#page=nn seems pretty useful. I'll implement it.

If there are other parameters from RFC 3778 you really care about, please file separate bug reports and mention "pdf plugin" in the report.
Status: Fixed
I've fixed this for the tip of the tree build. You should see this feature on future version of 13.x onwards.
Comment 6 by, May 13 2011
Thanks, thestig. I see this change showing up in the latest Canary builds. However, it seems that it is using a zero-based approach to showing the page. So, if I add #page=0 it opens to page 1, #page=1 opens to page 2, etc. The RFC seems a little vague on this detail, but I think it intends to open to the "physical" page - that is, one-based. Adobe's plug-in is one-based, so #page=1 opens to page 1, #page=2 opens to page 2, etc. Since we have Adobe's implementation in other browsers as a reference, can we update Chrome's behavior to match?
Doh. I thought I tested that. Will fix.
The page # off by one is fixed. It will likely make it into a dev channel release some time next week.
Comment 9 by, Jul 13 2011
Working fine in the 14.0.814.0
Status: Verified
I am running public release version 12.0.742.100 and this feature is working great now.  A belated thanks to thestig!
Comment 12 by Deleted ...@, Nov 10 2011
version 15.0.874.106 m - not working
Comment 13 by, Nov 10 2011
Works for me with that version on Linux using the link in the original bug report.
Project Member Comment 14 by, Oct 13 2012
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member Comment 15 by, Mar 11 2013
Labels: -Area-UI -Feature-PDF Cr-Content-Plugins-PDF Cr-UI
Project Member Comment 16 by, Apr 6 2013
Labels: Cr-Blink
Project Member Comment 17 by, Apr 6 2013
Labels: -Cr-Content-Plugins-PDF Cr-Internals-Plugins-PDF
Sign in to add a comment