Bug 165200 - Style dialog: Allow copying of textual style content
Summary: Style dialog: Allow copying of textual style content
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
24.8.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Styles-Dialog
  Show dependency treegraph
 
Reported: 2025-02-11 14:36 UTC by Eyal Rozenberg
Modified: 2025-02-13 23:22 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eyal Rozenberg 2025-02-11 14:36:11 UTC
Several LO style dialogs for styles have a "General" pane with a "Contains" header, followed by the textual description of what the style contains.

Users, especially for QA purposes and sometimes for collaboration, as well as developers, occasionally need to copy that text. Yet - the dialog does not allow for such a copy. 

To clarify: Just copying, not pasting.

MS Word allows this copying.
Comment 1 Heiko Tietze 2025-02-13 08:08:56 UTC
-1, we do not develop the app for QA. There is no use case that requires to interact with this plain information.
Comment 2 Eyal Rozenberg 2025-02-13 23:22:20 UTC
(In reply to Heiko Tietze from comment #1)
> There is no use case that requires to
> interact with this plain information.

Of course there is: Comparing styles. You have two styles which seem to serve mostly the same purpose, or behave the same; and you want to know if they actually are the same, and you can give up on one of them. Examining the text of their contents is what you're likely to do.

> -1, we do not develop the app for QA.

Heiko, what are you talking about? We have a complete localization for use only by translators; we have safe mode; we have debugging utilities; we have a special button in the About dialog, just to copy the build information; and that is not remotely all the things we offer, which users don't need and will never use, but QA people and developers - would and do.


In this case the ability is in no way detrimental to users. It doesn't take up space, it doesn't slow things down, it doesn't interfere with any workflow - nothing.