Date: prev next · Thread: first prev next last
April 2017 Archives by date, by thread · List index


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

Regina Henschel <rb.henschel@t-online.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rb.henschel@t-online.de

--- Comment #4 from Regina Henschel <rb.henschel@t-online.de> ---
@Heiko: This report is about managing the content of hierarchical styles in the
Style&Formatting dialog.

You can set a property back to 'inherit': In the style properties go to the
tab, which contains the property. Then click on button "Standard". Go back to
'Organizer' tab and look what has been removed.
Unfortunately there is no way to set a single property of the tab page back to
'inherit'.
And sometimes the property is removed but still shown in 'Organizer' tab.

There are similar requests in bug 89826, bug 77325 and bug 88921.

The second is about making the inheritance visible in the tab pages. I can
think of making the item "italic" or for field entries adding an indicator
before or after the content, e.g. '(i) 12pt' instead of simple '12 pt'. No idea
how to do it for other kind of controls.

The problem is very old see https://bz.apache.org/ooo/show_bug.cgi?id=3148

I support both requests.

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