Bug 198427 - Hyperlink hopping is inaccurate when "trim margins" is on
Summary: Hyperlink hopping is inaccurate when "trim margins" is on
Status: CONFIRMED
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 1.11.3
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-30 17:11 UTC by Claus Appel
Modified: 2021-04-05 14:22 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Claus Appel 2009-06-30 17:11:14 UTC
Version:           0.8.4 (using 4.2.4 (KDE 4.2.4), 4.2.4-2.fc11 Fedora)
Compiler:          gcc
OS:                Linux (i686) release 2.6.29.5-191.fc11.i586

When clicking a hyperlink in a PDF document, Okular normally hops to the target correctly. But if the "trim margins" feature is enabled (View -> Trim margins), Okular does not correctly hit the hypertarget. It will be scrolled down too low, so that the first lines under the hypertarget are invisible. The user has to manually scroll up to get to the intended target. 

Presumably this happens because "trim margins" resizes the displayed page "from the middle", so that the top and bottom of the page are pushed off-screen.
Comment 1 jordonwii 2012-01-05 05:34:43 UTC
Hi Claus,
Can you still reproduce this bug in the latest version of Okular? If so, please provide an example PDF.
Thanks.
Comment 2 Claus Appel 2012-01-05 11:25:49 UTC
Hi. I can reproduce it in Okular 0.12.5. (I know this isn't the latest version, but maybe it's useful.) I am using this file:

tobi.oetiker.ch/lshort/lshort.pdf

If I enable "Trim Margins" and "Fit Width" and then click on the link to "1.2 Basics", it scrolls down so that the heading "1.2 Basics" is not visible.
Comment 3 jordonwii 2012-01-05 15:15:22 UTC
This is working ok for me in Okular 0.13.3.
Comment 4 Albert Astals Cid 2012-01-05 19:31:05 UTC
jordon, it does not work, so probably you are not testing it correctly, this is a known bug, fixing it is not trivial, that's why it is not fixed, i'll set it as "NEW"
Comment 5 Justin Zobel 2021-03-09 23:59:23 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 6 Erik Quaeghebeur 2021-03-10 10:37:07 UTC
(In reply to Justin Zobel from comment #5)
> As this report hasn't seen any changes in 5 years or more, we ask if you can
> please confirm that the issue still persists.
The issue still persists (I tested again).