https://bugs.documentfoundation.org/show_bug.cgi?id=86606
--- Comment #18 from Octavio Alvarez <octallo@alvarezp.org> ---
I also consider the bug merging to be a mistake, as neither bug has anything to
do with the other one.
This bug talks about removal of individual DF attributes from the context menu,
while #100604 talks about the state of the "Clear DF" context menu item not
being context-aware.
Comment #16 just makes no sense and just introduced noise. It talks about the
control state in the toolbar and the menu bar, but the original bug has nothing
to do with it. It states that "Direct formatting has been removed from the
default configuration of the context menu", it apparently implying that "Clear
DF" is removed too or should be removed too.
Now both bugs are confusing, as there is now some implication that "Clear DF"
is or should be removed from the context menu, but "Clear DF" *has not* been
removed from the context menu, and...
"Clear DF" *should not* be removed from the context menu because the context
menu *still has* DF in the form of the "Character..." and "Paragraph..." menu
items, as opposed to what was stated in comment #16.
I agree they are related, though, so "See also" might be a good idea and
possibly appropriate, but "duplicate" is definitely false.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 86606] CONTEXT MENU: Removal of remaining direct formatting entries · 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.