<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Writer sidebar minimum width is too wide when docked (see comment 16 comment 22)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=131947#c33">Comment # 33</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Writer sidebar minimum width is too wide when docked (see comment 16 comment 22)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=131947">bug 131947</a>
from <span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span></b>
<pre>(In reply to Christian Lehmann from <a href="show_bug.cgi?id=131947#c32">comment #32</a>)
<span class="quote">> ...
> However, I still miss an argument why the controls cannot be arranged in two
> rows from start, esp. if the same is acceptable on the navigation bar (and
> in several other menu windows, for that matter).</span >
You of course mean the Navigator <F5> deck, the 'Navigation Bar' is a standard
two button toolbar.
The Navigator deck (floating <F5>, or Sidebar resident) is constrained as all
other decks. The Content panel controls are in two rows because that is what
functionally makes sense--while the deck width is controlled by the Navigate by
listbox, its Previous/Next buttons, and the Goto Page spin box. Or rather by
the calculated width of those controls.
The layout of the Sidebar is deliberate and suited to task.
There is nothing to be gained by reworking the content panels of the decks into
layouts that consume vertical space to reduce width of the deck, and a lot to
be lost by losing the contextual relationship between blocks of controls.
The Sidebar assemblage was always intended to optimize visibility of controls
by making use of the extra horizontal space on a display. As opposed to the
menu/toolbar paradigm alone which consumes vertical space on the display to
expose more controls.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>