<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Context toolbar make jumping ui" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124835#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Context toolbar make jumping ui" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124835">bug 124835</a> from <a class="email" href="mailto:momonasmon@gmail.com" title="Maxim Monastirsky <momonasmon@gmail.com>"> Maxim Monastirsky</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=124835#c9">comment #9</a>) > @Maxim, Samuel -- any thoughts on <a href="show_bug.cgi?id=124835#c3">comment 3</a>, idea of pushing toolbars > activated as context onto a Sidebar content panel? Sorry, but I don't like this idea. IMHO everything which is in the sidebar by default, should be done in a "sidebar way" - meaning having dedicated and carefully designed panels/decks. The sidebar already deals with context-related stuff in its "Properties" deck - that what it was designed for, with panels for text, images, shapes etc. And likewise there should be panels for all other contexts (e.g. tables in Writer), not just as a generic "toolbar inside a sidebar container" kind solution. And <a class="bz_bug_link bz_status_NEW " title="NEW - Sidebar: as container for toolbars, ability to add functions missing from Sidebar" href="show_bug.cgi?id=33223">bug 33223</a> is unrelated, because it talks about some customization possibility, while here we talk about the default sidebar behavior wrt contextual commands. So I agree with Andreas that the sidebar mode should consist of a standard toolbar (which also server as a place for customization, as the sidebar itself isn't and won't be customizable to the level of toolbars) + the sidebar, and no other context toolbars popping ever.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>