Bug 122270 - Tabbed Notebook Bar (Impress) View (tab) Normal and Master buttons do not properly update UI when user switches view
Summary: Tabbed Notebook Bar (Impress) View (tab) Normal and Master buttons do not pro...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.2.0.1 rc
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Notebookbar-Tabbed
  Show dependency treegraph
 
Reported: 2018-12-21 17:13 UTC by Drew Jensen
Modified: 2022-11-22 10:30 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
Graphic which shows issue (322.95 KB, image/png)
2020-02-24 22:15 UTC, Drew Jensen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Drew Jensen 2018-12-21 17:13:08 UTC
Test system Ubuntu 18.04.1 (AMD64), LO 6.2.0.1 RC1

To reproduce:

1 - Open any Impress file with the Tabbed Notebook Bar UI activated
2 - Switch to the View tab
3 - Click on the 'Master Slide' button

result:
The content view changes to the master slide, the notebook bar UI does not update which button now has focus. It still displays the 'Normal' button with the 3d effect, this should now be flat and the effect on 'Master Slide' button.

4 - Click on the 'Slide Sorter' button

result:
The notebook bar UI updates properly and 'Slide Sorter' has the 3d effect.

5 - Click on the 'Master Slide' button

result:
The notebook bar UI updates properly and 'Master Slide' has the 3d effect.

6 - Click on the 'Normal' button

result:
The notebook bar does not update properly and the 3d effect does not change to the proper button.
Comment 1 Roman Kuznetsov 2018-12-21 20:42:22 UTC
confirm in

Версия: 6.2.0.1
ID сборки: 0412ee99e862f384c1106d0841a950c4cfaa9df1
Потоков ЦП: 4; ОС:Linux 4.13; Отрисовка ИП: по умолчанию; VCL: gtk3; 
Локаль: ru-RU (ru_RU.UTF-8); UI-Language: ru-RU
Calc: threaded
Comment 2 Rizal Muttaqin 2020-02-24 18:39:30 UTC
(In reply to Drew Jensen from comment #0)
> Test system Ubuntu 18.04.1 (AMD64), LO 6.2.0.1 RC1
> 
> To reproduce:
> 
> 1 - Open any Impress file with the Tabbed Notebook Bar UI activated
> 2 - Switch to the View tab
> 3 - Click on the 'Master Slide' button
> 
> result:
> The content view changes to the master slide, the notebook bar UI does not
> update which button now has focus. It still displays the 'Normal' button
> with the 3d effect, this should now be flat and the effect on 'Master Slide'
> button.
> 
> 4 - Click on the 'Slide Sorter' button
> 
> result:
> The notebook bar UI updates properly and 'Slide Sorter' has the 3d effect.
> 
> 5 - Click on the 'Master Slide' button
> 
> result:
> The notebook bar UI updates properly and 'Master Slide' has the 3d effect.
> 
> 6 - Click on the 'Normal' button
> 
> result:
> The notebook bar does not update properly and the 3d effect does not change
> to the proper button.

Please elaborate what do you mean with 3d effect better with screenshot per step
Comment 3 Drew Jensen 2020-02-24 22:15:24 UTC
Created attachment 158150 [details]
Graphic which shows issue

OK - here is an image that shows the problem.

First I am again on Ubuntu 18.04, but this is using the latest LO-Dev 7.0 build.

I was trying to point out in the earlier 'how to recreate' is that the Master Slie button is only left without the visual clue that it has been selected when the user clicks on it while the Normal View button is active.

If you click on any of the other buttons first, ie Slide Sorter, and the Master View the visual clue that Master View button was selected works.

The problem works the other way also.
If the user clicks on the Normal View button while the Master View button has the highlighting then the view changes but the Normal Button does not show the highlighting. Again, if any other combination of From -> To buttons is used the highlighting works as expected.
Comment 4 QA Administrators 2022-02-24 03:36:38 UTC
Dear Drew Jensen,

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 https://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://web.libera.chat/?settings=#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug