Date: prev next · Thread: first prev next last
August 2018 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=119275

V Stuart Foote <vstuart.foote@utsa.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Right-click section title   |Right-click Content Panel
                   |in Side Bar to expand that  |Title in Side Bar Deck to
                   |section and at the same     |expand that content panel
                   |time collapse all other     |and at the same time
                   |sections                    |collapse all other content
                   |                            |panels on that Deck
                 CC|                            |vstuart.foote@utsa.edu

--- Comment #3 from V Stuart Foote <vstuart.foote@utsa.edu> ---
The Content Panels are now stateful--recorded into user profile.

We can already toggle visible or hidden *each* Content Panel with its toggle
arrow. 

Not sure the UX of a context menu collapse of all Content Panels would be well
received as it would blow away any prior panel state recorded to profile.

User beware, but it seems a bit heavy handed for what can be achieved more
precisely to work flow with just a couple of mouse clicks to toggle the
visibility of each panel on a deck.

-- 
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.