https://bugs.documentfoundation.org/show_bug.cgi?id=153623
--- Comment #13 from ajlittoz <page74010...@yahoo.fr> --- Understanding style inheritance (within a category PS or CS) and interaction (when applying CS over PS) is already difficult enough so that you must not add any complexity to the present dialog(s). What is needed (requested?) is a visual clue that an attribute has not been explicitly set or unset. Checkboxes already have a long-recognised aspect for tri-state: no tick, ticked and grayed. This is not used in LO but could be, provided some hint mentions in built-in help that gray does not mean "disabled" but "inherited". For lists, you could display the values gray and the selected one standard (black). Clicking on another item selects it. Clicking on the selected one deselects it and sets it to "inherited", i.e. gray again. I suggested gray but if you have a better idea, notably to avoid confusion with "disabled", you're welcome. Everything else can remain as is. RGB complains about sample display in CS. Unfortunately, nothing can be done about it. CS can be applied over ANY PS. Therefore, we know nothing about effective font face (unless it is overridden in CS inheritance). Using application-wide or document-wide default for sample display makes perfect sense. The problem here is understanding of the style feature by newbies. Unless they read documentation, which very few do. -- You are receiving this mail because: You are on the CC list for the bug.