https://bugs.documentfoundation.org/show_bug.cgi?id=90374
V Stuart Foote <vstuart.foote@utsa.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEEDINFO
CC| |vstuart.foote@utsa.edu
Ever confirmed|0 |1
--- Comment #1 from V Stuart Foote <vstuart.foote@utsa.edu> ---
@Jay,
IMHO do not agree *at all*. A fixed Sidebar Deck area locks us into a fixed
Sidebar layout. Stretching and shrinking the Sidebar is needed to accommodate
dynamic use of the Sidebar as any future content panels are implemented, or
users roll their own content panels.
This suggestion is 100% opposite of bug 83526#c5 - "Deck not adjusted for
content panel size when switching content panels"
Adjustments to the Sidebar should be a simple and convenient as currently
available to customize Toolbars, they are not (some annoyances listed below).
The Sidebar deck and user preferences should be stateful and user configured,
and work on bug 85905 - "Allow undocking of Sidebar decks" pursued to allow the
Sidebar to become fully functional.
=-Sidebar annoyances-=
bug 33223 - Sidebar: as container for toolbars, ability to add functions
missing from Sidebar
bug 65351 - Sidebar: open pane that was active when last used
bug 67230 - Sidebar does not keep state of Content View in Navigator
bug 67770 - Sidebar customization settings not remembered after reopening
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.