https://bugs.documentfoundation.org/show_bug.cgi?id=128960
--- Comment #19 from V Stuart Foote <[email protected]> ---
(In reply to Heiko Tietze from comment #18)
> (In reply to Ahiijny from comment #17)
> > Just to add another perspective from a new user point of view:
>
> The issue is clear. But the requested button to remove a CS is not the
> solution to a missing understanding (not blaming the user by this but design
> and workflow) or the awkward way to revert CS by setting Default.
By the same token, a single "well placed/named/tool-tipped" button action is
self documenting and would itself provide some insight for users.
> Rather
> feedback is key here- and the proposal is under
> https://design.blog.documentfoundation.org/2019/11/05/proposal-to-
> conveniently-highlight-and-inspect-styles-in-libreoffice-writer/
Well, this should still probably happen, but inspection and highlighting is a
much more complex/ambitious "solution" for Style visualizations, while this
otherwise a simple requirement for a single .uno action to remove applied
Character Style(s) from selection and _simply_ to restore the attributes
provided by the applied Paragraph Style.
Simplicity for a UX solution now, and pursue more dev interest/effort to fully
implement proposed visual manipulation of styles going forward.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
