Clicking on a link to a heading or on a task does not always scroll to the right position

[Nick222]

By clicking on a link to a place or heading in a note, you simply go to the note - not to the given heading or the given place of the link.

Xubuntu 21.04
Zim 0.74.1

(I think - it is bug?)

[jaap-karssenberg]

I believe it is related to loading inline objects which change the scroll position - see _hack_on_inserted_tree() in pageview/__init__.py Can you confirm this happens only on pages with objects (equations / code blocks /...) ? Need investigation how to solve issues with rendering objects :(

…

On Fri, Sep 24, 2021 at 1:25 PM Nick222 ***@***.***> wrote: By clicking on a link to a place or heading in a note, you simply go to the note - not to the given heading or the given place of the link. Xubuntu 21.04 Zim 0.74.1 (I think - it is bug?) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1617>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJQYHXUSTKFI5D546HS6FLUDRNZXANCNFSM5EVXYXIA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[Nick222]

Zim version 2021-09-28:

Pages without any objects - and with objects - both

• link to heading - OK - except if this heading is nearly end of note
• link to special place (##note) - OK - except if this place is nearly end of note

And - can user create link on object - and how? What it is "object id" - as write in manual?

[jaap-karssenberg]

Sorry, I don't understand you. By "OK" do you mean there is no issue anymore ?

…

-- Jaap

On Wed, Sep 29, 2021 at 10:00 AM Nick222 ***@***.***> wrote: Zim version 2021-09-28: - link to heading - OK - except this place nearly end of note - link to special place (##note) - OK - except this place nearly end of note And - can user create link on object - and how? What it is "object id" - as write in manual? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1617 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJQYHSQXD46YPFV6RLZDOTUELBS3ANCNFSM5EVXYXIA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[Nick222]

OK = work good (going to right place)

[aqeeliz]

Same issue here. On Arch Linux, zim-wiki version 0.74.2

If I make a link to heading on same page #some-heading, it works fine.

When linking "Some Heading" from some other page, :SomePage#some-heading, it opens SomePage, but doesn't scroll down to the heading. It takes the cursor to correct place though, so if you press "up" or "down" on keyboard, you scroll to right place.

I have tried on three different pages, I get the above mentioned issue on 2 pages, both of these pages only have headings and bullet lists (they are very long pages).

Linking to heading works fine on a small page though, and this page also has images and diagrams in it.

[sojusnik]

Happens here as well on Ubuntu 21.10 with 0.74.2.

It seems that the longer the page, the larger the offset.

Could be connected to
#611
#770

[jaap-karssenberg]

No, it is not related to the two issues quoted above.

Interestingly this only happens when switching to a new page. It does not happen only for links to headings, but also when e.g. clicking on a task in the side pane. This means it is behavior related to the "scroll on screen" generic function. But if the page is shown and I click again the same tasks, it does scroll correctly. So seems to be a timing issue between rendering the new page and scrolling. Tried fixing it with a callback on a timer, but that didn't help :(