My favorites | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 65851: Navigation in PDF based on page# in URL - nice to have feature
25 people starred this issue and may be notified of changes. Back to list
Status:  Verified
Owner:  thestig@chromium.org
Closed:  May 2011

Restricted
  • Only users with Commit permission may comment.


Sign in to add a comment
 
Reported by m...@janmach.cz, Dec 8, 2010
Chrome Version       : 8.0.552.215
URLs (if applicable) : http://nusl.techlib.cz/images/Book.pdf#page=11
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.
Dec 11, 2010
#1 Satoshi.Matsuzaki@gmail.com
This works with Adobe's PDF Plug-In.
Labels: -Area-Undefined Area-UI Feature-PDF
Jan 12, 2011
#2 pav...@google.com
(No comment was entered for this change.)
Summary: Navigation in PDF based on page# in URL - nice to have feature
Status: Untriaged
Labels: -Pri-2 Pri-3
Apr 4, 2011
#3 m...@janmach.cz
Another parameters in RFC 3778 chapter 3: http://tools.ietf.org/html/rfc3778
May 9, 2011
#4 thestig@chromium.org
#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: Started
Owner: thestig@chromium.org
May 9, 2011
#5 thestig@chromium.org
I've fixed this for the tip of the tree build. You should see this feature on future version of 13.x onwards.
Status: Fixed
May 13, 2011
#6 brya...@gmail.com
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?
May 16, 2011
#7 thestig@chromium.org
Doh. I thought I tested that. Will fix.
May 18, 2011
#8 thestig@chromium.org
The page # off by one is fixed. It will likely make it into a dev channel release some time next week.
Jul 12, 2011
#9 raya...@google.com
Working fine in the 14.0.814.0
Jul 13, 2011
#10 pavanv@chromium.org
(No comment was entered for this change.)
Status: Verified
Sep 12, 2011
#11 jasony...@verizon.net
I am running public release version 12.0.742.100 and this feature is working great now.  A belated thanks to thestig!
Nov 9, 2011
#12 fanis.gi...@gmail.com
version 15.0.874.106 m - not working
Nov 9, 2011
#13 thes...@google.com
Works for me with that version on Linux using the link in the original bug report.
Oct 13, 2012
#14 bugdro...@chromium.org
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.
Labels: Restrict-AddIssueComment-Commit
Mar 10, 2013
#15 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Area-UI -Feature-PDF Cr-Content-Plugins-PDF Cr-UI
Apr 5, 2013
#16 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: Cr-Blink
Apr 5, 2013
#17 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Cr-Content-Plugins-PDF Cr-Internals-Plugins-PDF
Sign in to add a comment

Powered by Google Project Hosting