Step to reproduce: - open a document with at least one bookmark; for example open https://bugs.documentfoundation.org/attachment.cgi?id=125972 - right click on the Page number field on the left end of the status bar; you see a dropdown list of the available bookmarks - select one of the bookmarks expected behavior: the cursor jump to the bookmark position in the text; if the bookmark is not in the visible part of the document, the document moves in order to show the document part where the bookmark is. current behavior: the document moves if necessary, but the cursor is not visible. No problem if you double-click on a the same bookmark in the Navigator. In this case the cursor is visible. Version: 5.2.1.0.0+ Build ID: a2890a3fcdfcbf2447871ebc23db47864dd5b215 Threads CPU : 4; Version de l'OS :Linux 4.4; UI Render : par défaut; Ubuntu_16.04_x86-64 Locale : fr-FR (fr_FR.UTF-8); Calc: single built at home and used with GTK 2 plugin. Best regards. JBF
Confirming on Windows 10 Pro 64-bit en-US with Version: 5.2.0.3 (x64) Build ID: 7dbd85f5a18cfeaf6801c594fc43a5edadc2df0c CPU Threads: 8; OS Version: Windows 6.19; UI Render: GL; Locale: en-US (en_US) After creating a new ODT document in Writer and setting a couple of bookmarks, saving and reopening. Using the Status bar page field context menu list of bookmarks. The document canvas scrolls to the bookmark when selected, but the edit cursor does not reposition.
I see the problem in 5.3, but not in 3.6 Arch Linux 64-bit, KDE Plasma 5 Version: 5.3.0.0.alpha0+ Build ID: f3d26af51588af441f62fb69bb7a5432845226ac CPU Threads: 8; OS Version: Linux 4.6; UI Render: default; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on August 5th 2016 Arch Linux 64-bit Version 3.6.7.2 (Build ID: e183d5b)
I can only reproduce it with GTK2, not with GTK3. Adding it to the summary... Regression introduced in range c1b90fa342e09ab30068f6294fc866c63d7ae4c4..00cf864e5d317016d7224c199aa982d07bd70113 Caolán, One for you?
*** This bug has been marked as a duplicate of bug 101884 ***
@Caolán -- wass that the correct issue to duplicate to? Seems a tad unrelated.
Think this was intended to be a dupe of bug 102177 *** This bug has been marked as a duplicate of bug 102177 ***