UI: Navigator content not refreshed after renaming a page/slide in Draw/Impress
Steps to Reproduce:
1. Open Draw
2. Set sidebar to Navigator
3. Right Click they slide/page panel & select rename
4. Type something and apply
5. Notice the name not being updating in navigator
6. Switch deck.. still not updating
Navigator isn't refreshed after page name change
Should be so
User Profile Reset: No
Version: 188.8.131.52.alpha0+ (x64)
Build ID: 94e6e140491de31c0788c91af855a75a3bb12709
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Also found in
Changing deck triggers and update with 184.108.40.206 (so this partly a regression)
Adding a new slide, and the deck is updated
This is something you might be interested in or an easy hack, I guess
I repro the sidebar Navigator not updating. The F5 floating Navigator updates as expected.
Here is a patch that makes sidebar Navigator update as expected:
*** This bug has been marked as a duplicate of bug 106613 ***
Let me explain QA:
Normally we mark newer a duplicate of older.
Sometimes we reverse, when fix is in the newer bug because it's more simple and better defined.
But here as times before, Telesto made a duplicate although better defined and easily searchable bug is present. So reverse logic is not justified here.
Invited dev spent time to find out what's already known, difference between sidebar Navigator and floating Navigator.
(In reply to Timur from comment #5)
> Let me explain QA:
> Normally we mark newer a duplicate of older.
> Sometimes we reverse, when fix is in the newer bug because it's more simple
> and better defined.
> But here as times before, Telesto made a duplicate although better defined
> and easily searchable bug is present. So reverse logic is not justified
Yes, I missed they duplicate.. and yes, this is additional work for DEV to adjusting the bug number..
> Invited dev spent time to find out what's already known, difference between
> sidebar Navigator and floating Navigator.
They STR is not that bad, I think. I assume Developers check stuff themselves anyhow. In bug 106613 you need to read through different comments too. So I assume it's OK
Also they bottom line: it's solved.