https://bugs.documentfoundation.org/show_bug.cgi?id=119919
Heiko Tietze <tietze.heiko@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #2 from Heiko Tietze <tietze.heiko@gmail.com> ---
The hide/show functionality does not work at all. Tried with Test (None), 1
(Test), 2 (1) and hid 1 which makes 2 disappear. Some other test with default
styles were as described but cannot rerun for some reason.
Besides I agree with Thomas that hiding children is awkward. OTOH it also is
weird when your tree suddenly switches from Foo > Bar > Qux to Bar > Qux after
hiding Foo. So either we keep the hidden styles alive in the tree and just grey
them out or select the first children, in the example Bar to keep the position.
"Hide tree" (or the like) as additional command is also an option.
Some styles must not be hidden, Default for example - not only when used. I can
do so for Text Body but this item is still shown then. Maybe my test program is
not up tp date.
Version: 6.0.4.5
Build ID: 6840e4519a6ce8bcc1328eb2d87b5c46c6df1038
CPU threads: 4; OS: Mac OS X 10.13.6; UI render: default;
Locale: de-DE (de_DE.UTF-8); Calc: group
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 119919] Non-hidden children of hidden styles appear in top level of sidebar · bugzilla-daemon
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.