The Navigator loses multi-selection of node items one second after right-clicking on the selection. For me, there's nothing in the context menu that shouldn't be usable through multi-selection and that justifies the disappearing of the multi-selection.
Steps to reproduce:
1. Open or create a Writer document with several headings.
2. Open Navigator (F5) or go to the Navigator pane in the Sidebar.
3. Make sure that a heading is selected in the Navigator and not a table, hyperlink, etc.
4. Open the 'Content Navigation View' with the button at the bottom and left-most position in the Navigator button area.
5. Select multiple headings with ctrl + mouse clicks or shift + mouse clicks.
6. Right-click at one of the selected headings (not at another not-selected heading).
After about a second, the multi-selection disappears and only the heading is selected where the cursor is in the document.
The multi-selection doesn't disappear.
Tested with Version: 18.104.22.168 (x64)
CPU-Threads: 8; BS: Windows 10.0; UI-Render: Standard;
Gebietsschema: de-AT (de_AT); Calc: group
and Version: 22.214.171.124.alpha0+ (x64)
Build ID: 89a60912bba7ffd6f65ea99f4664f343c5025c95
CPU threads: 8; OS: Windows 10.0; UI render: GL;
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-01_03:18:33
Locale: de-AT (de_AT); Calc: CL
Repro on Win, not on Lin. Tested with attachment 145437 [details]
Multi-selection does not work for me in 6.1.2, but I guess that might be something Jim fixed for 6.2.0.
Arch Linux 64-bit
Build ID: 9a373521d7a328197a4bf9abeb0a981b7acba896
CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
Locale: fi-FI (fi_FI.UTF-8); Calc: threaded
Built on 19 October 2018
Version: 126.96.36.199.alpha1+ (x64)
Build ID: 8274c4c62df5b937b3f0bec9e1eeca85f3b219d4
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win;
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-22_01:47:50
Locale: fi-FI (fi_FI); Calc: threaded
Dear Thomas Lendo,
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Hi Thomas and Buovjaga,
Bug 128285 is a duplicate of this bug report with a recently merged patch. I would have filed it under this one but didn't know it existed until just now while searching through recent list of untouched bugs.
Ok, fine, let's dupe this to it :)
*** This bug has been marked as a duplicate of bug 128285 ***