Bug 40433 - Useful WM_CLASS and WM_ROLE properties
Summary: Useful WM_CLASS and WM_ROLE properties
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected)
Hardware: Other All
: medium minor
Assignee: Not Assigned
Depends on:
Reported: 2011-08-28 05:16 UTC by Christoph Kappel
Modified: 2016-09-20 10:18 UTC (History)
0 users

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Kappel 2011-08-28 05:16:44 UTC
Currently, LibO uses rather confusing values for the WM_CLASS property and doesn't use WM_ROLE at all. It would be really helpful for tagging window managers and probably session managers as well, when named properties contain useful values.

I haven't checked the values for all LibO windows, but here are the values for  Calc and Impress:

WM_CLASS(STRING) = "VCLSalFrame.DocumentWindow", "libreoffice-calc"
WM_CLASS(STRING) = "VCLSalFrame", "libreoffice-impress"

My suggestion is to use something like:

WM_CLASS(STRING) = "calc", "libreoffice"
WM_ROLE(STRING)  = "libreoffice-calc"

Additonally the presentation window of Calc has even stranger properties:

WM_CLASS(STRING) = "VCLSalFrame", "LibreOffice 3.4"

My suggestion here:

WM_CLASS(STRING) = "calc-presentation", "libreoffice"
WM_ROLE(STRING)  = "libreoffice-calc"

The output and my suggestions use the output format of xprop.
Comment 1 Björn Michaelsen 2011-12-23 12:38:27 UTC Comment hidden (obsolete)
Comment 2 QA Administrators 2014-06-25 17:37:59 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2015-07-18 17:43:59 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2016-09-20 10:18:07 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice 
(5.1.5 or 5.2.1  https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and 
your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave 
a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)


2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword

Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team