Bug 98762

Summary:	UI: Navigation toolbar keeps appearing even after View -> Toolbar -> Navigation toolbar is deselected
Product:	LibreOffice	Reporter:	Ljiljan <lilicus>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	raal, vsfoote
Priority:	medium
Version:	4.0.0.3 release
Hardware:	All
OS:	All
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	108816

Description Ljiljan 2016-03-19 07:33:14 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36
Build Identifier: LibreOffice 5.1.0.3

Common behaviour of toolbars in LibreOffice is that it appears when you need it, but once you deselect the toolbar, LibreOffice should remember that you don't need this toolbar. And it works with the most toolbars. However, Navigation toolbar keeps appearing even after de-selecting it in View->Toolbars-> Menu.

Reproducible: Always

Steps to Reproduce:
1. Insert Bookmark somewhere. 
2. Use any action related to bookmark (such as you go to third page, and click on the bookmark so you go back or right click on the status bar where page number is shown and select the bookmark)
3. Navigation toolbar will appear
4. Go to View -> toolbars -> Navigation bar and de-select it.
5. Navigation toolbar disappears.
6. Try to use any action related to bookmarks and it will appear again.

Actual Results:  
Navigation toolbar keeps appearing after user decide not to use it (disable it).

Expected Results:  
Navigation toolbar should be hidden once user decided not to use it (disable it).

[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes


Reset User Profile?No

Comment 1 raal 2016-03-21 07:16:49 UTC

I can confirm with Version: 5.2.0.0.alpha0+
Build ID: 45701913f642b17aabd67b52de9002cc79cf07ae
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
and Version 4.0.0.3

Comment 2 QA Administrators 2017-05-22 13:19:54 UTC Comment hidden (obsolete)

** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice
(5.2.7 or 5.3.3 https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and
your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System

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)

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: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug-20170522

Comment 3 Christian Lehmann 2018-05-04 09:47:14 UTC

I commented on this, using bug number 49710.

Comment 4 Thomas Lendo 2018-05-05 01:27:29 UTC


*** This bug has been marked as a duplicate of bug 49710 ***

Comment 5 V Stuart Foote 2018-05-05 01:40:26 UTC


*** This bug has been marked as a duplicate of bug 115817 ***