https://bugs.documentfoundation.org/show_bug.cgi?id=112852
--- Comment #17 from Yousuf Philips (jay) <philipz85@hotmail.com> ---
(In reply to Mike Kaganski from comment #14)
I suppose that the best is to focus on something like described in comment
9. This (or some similar) would *enable* one to see and understand what is
going on.
Yes a similar concept has already been proposed in bug 90646 (mockup:
attachment 115020). MS Word's Style Inspector dialog is a good implementation
of the same concept, while a browser's DOM inspector implementation is way to
complicated.
http://img-aws.ehowcdn.com/default/cme/photography.prod.demandstudios.com/9d4dd6bd-c8cf-4fc4-a385-ccd1b671ae6a.png
Without means to understand, any "resolution" would only confuse
another group. Only when there's a view of the formatting structure, can we
start to think about Benjamins (because only then can we start to implement
easier tooling around the advanced structure viewer).
Benjamins primarily dont deal with styles, so this functionality isnt focused
on them.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 112852] Should unapplying Bold remove the attribute or force text to Regular? · 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.