Closed Bug 839092 Opened 11 years ago Closed 11 years ago

Clicking on titles from Show Document Outline does not always bring up on top of the page the title selected

Categories

(Firefox :: PDF Viewer, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: bmaris, Unassigned)

Details

Reproducible on the latest Aurora (BuildID: 20130206042020):
Mozilla/5.0 (Windows NT 6.1; rv:20.0) Gecko/20130206 Firefox/20.0
Reproducible on the latest Nightly (BuildID: 20130207030936): 
Mozilla/5.0 (Windows NT 6.1; rv:21.0) Gecko/20130207 Firefox/21.0
Reproducible on FF 19 beta 5 (BuildID: 20130206083616):
Mozilla/5.0 (Windows NT 6.1; rv:19.0) Gecko/20100101 Firefox/19.0

Steps to reproduce:
1. Open this PDF (http://developer.amd.com/wordpress/media/2012/10/43009_sb7xx_rrg_pub_1.00.pdf.
2. Wait for the pdf to load and then click on Toggle Slider (left button).
3. Click on the Show Document Outline and then click on Introduction (The title is right on top of the page).
4. Click on About this Manual, right under Introduction (The title is not shown, a scroll up will reveal the title).
5. Click on Nomenclature and Conventions, right under About this Manual (The title is half shown).

Expected results: Clicking every title located in Show Document Outline shows the title selected on top of the page.

Actual results: Some titles are half shown or not shown at all.

Notes:
1. This issue not a regression, it reproduces on FF 16.0.1 where the pref "pdfjs.disabled" is set to false for the pdf.js to be enabled.
Bogdan, does the Adobe Reader do the same?
Happens exactly the same for me in Adobe Reader 11. I'm assuming this is just a misplaced bookmark within the document itself. Resolving INVALID.

Bogdan, please confirm and compare against Adobe Reader in the future.

Thank you
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Yes this is the same behaviour with Adobe Reader 11 and Foxit Reader too. Thanks for the observation, in the future I will look into it more carefully.
You need to log in before you can comment on or make changes to this bug.