<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Correct implementation or remove the Navigation toolbar (a GSOC 2009 contribution see bug 32869) (comment 3 for history and functional intent)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=115817#c48">Comment # 48</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Correct implementation or remove the Navigation toolbar (a GSOC 2009 contribution see bug 32869) (comment 3 for history and functional intent)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=115817">bug 115817</a> from <a class="email" href="mailto:raykowj@gmail.com" title="Jim Raykowski <raykowj@gmail.com>"> Jim Raykowski</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=115817#c47">comment #47</a>) > The Navigation TB is nicely suppressed now. But when opened, it immediately > tracks the stack the same as the 'Recency' mode in Navigator. > Noticed that Navigation toolbar doesn't reappear if it was in the toolbar layout at exit. Patch is in progress of being approved by Jenkins. > Sidebar, do you think we'd need a way for user to reset and force clear the > navmgr stack during an edit session? Or just as now where a save, close and > reopen is enough to reset? We could add an UNO command to do this. FWIW, I never want the recency stack to clear in the ide I use, but it does and I'm not sure why :( Maybe if it didn't, I would want a way to clear it :) > @Jim, as I finished this I saw you had to tweak things with > <a href="https://gerrit.libreoffice.org/c/core/+/109504">https://gerrit.libreoffice.org/c/core/+/109504</a>, hope it still works as well > with navigate back and navigate forward controls. If it rolls tomorrow I'll > be able to compare. The patch fixes a bug when back navigation is done from a drawing object. It can be seen using the Navigation toolbar back button. It does not happen when using the Navigate-by Recency back button.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>