<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#c14">Comment # 14</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:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> V Stuart Foote</a> <pre>(In reply to andreas_k from <a href="show_bug.cgi?id=124835#c13">comment #13</a>) > Ok than l will do an single line notebookbar to replace the single line > toolbar. > Don't know that we need to replace the Single toolbar mode that Jay did with a Notebook bar--but it might be another MUFFIN to provide. > For the sidebar layout which contextual item isnt available in the sidebar? > I really like to bring all layouts in an good shape. No, if we are to adopt Single toolbar mode with a Sidebar deck to hold any context sensitive toolbars--they would need to go into a Content panel holding just the controls for the Toolbar as customized by user. We could not use an exiting Content panel--widgets positioned to different panels would be horrible UX. Rather, think here the Deck would contain the elements of what would otherwise pop-up in the activated context sensitive toolbar--but packed into a Content panel. Perhaps with a Tab bar button widget to toggle the behavior: 1.) show context sensitive Toolbar(s) as Toolbar, 2.) show context sensitive Toolbar(s) packed onto a Sidebar content panel (maintain use customizations of selection and sequence) when activated.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>