Date: prev next · Thread: first prev next last
October 2016 Archives by date, by thread · List index


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

Cor Nouws <cno@nouenoff.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NOTABUG                     |---

--- Comment #12 from Cor Nouws <cno@nouenoff.nl> ---
Hi Stuart,

Thanks for the new arguments. However, to me it looks that this command has
been removed maybe in a slip..

(In reply to V Stuart Foote from comment #8)
@Cor, *

It was removed during Maxim's work on making all src based context menus
user customizable implementing XML configuration for bug 93837 

For now, I have see no argumentation to remove that specific command.

Followed recommended simplifications of the context menu per Design UX
decision as argued in bug 81132 and bug 86606

Which is a good thing in general.

With XML based customization now supported--no reason to keep unhelpful
defaults in the context menus.

I don't think it's unhelpful at all.
Copy/Cut/Paste are in the context menu, main menu, toolbars and have shortcuts.
Clear Direct Formatting is maybe not that often used, but at least as
important.

See also my arguments in comment 7.

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