Description: Dear all, On LibreOffice 4.2 (GTK2) and LibreOffice 5.4 (GTK3) when I open the print dialog an AT-SPI2 "object:state-changed:checked" about formatting mark is sent. This event signify that the "formatting mark" will be printed but it is not the behavior. Steps to Reproduce: 1. Open the attached python listener 2. Launch LibreOffice 3. Press ctrl+p Actual Results: AN "object:state-changed:checked" event is emitted by LibreOffice Expected Results: No "object:state-changed:checked" event should be emitted because the user doesn't activate "formatting marks" Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Created attachment 135292 [details] object:state-changed:checked events listener
Hello, I can't reproduce on openSUSE Tumbleweed with LO print dialog.
(In reply to Arnaud Versini from comment #2) > Hello, > > I can't reproduce on openSUSE Tumbleweed with LO print dialog. I forgot to mention if you have formatting mark enabled the issue disappears. You also need to use the GTK2 or GTK3 front-end and to have accessibility enabled in your DE. Best regards.
Repro. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha0+ Build ID: 3c49b28ffa7ab062726e5e600312d9164224404e CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on August 26th 2017
** 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I can reproduce this: Version: 6.3.0.0.alpha0+ Build ID: f23738139429358c11fa62708fbdf5bb0c43d199 Threads CPU : 12; OS : Linux 4.19; UI Render : par défaut; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-02-28_20:14:57 Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded
Created attachment 180502 [details] updated listener script for python3 and output the event data
The specific bogus "formatting mark" one appears to have disappeared during the 6.1 cycle between 7f9b0f47979dcb7abfed37bb7cd38ab51eac6011 and 57ca02a7486090f1dd63977bb8fb351f9bf9a7f3 checking trunk today I have ... event object:state-changed:checked received [application | soffice] object:state-changed:checked(1, 0, 0) source: [check box | Page background] host_application: [application | soffice] sender: [application | soffice] event object:state-changed:checked received [application | soffice] object:state-changed:checked(1, 0, 0) source: [check box | Images and other graphic objects] host_application: [application | soffice] sender: [application | soffice] event object:state-changed:checked received [application | soffice] object:state-changed:checked(1, 0, 0) source: [check box | Form controls] host_application: [application | soffice] sender: [application | soffice] event object:state-changed:checked received [application | soffice] object:state-changed:checked(1, 0, 0) source: [check box | Print automatically inserted blank pages] host_application: [application | soffice] sender: [application | soffice] all these really are in the print dialog so that at least makes some sort of sense. The reason these get emitted is because the a11y objects for the checkboxes are created early because those checkboxes happen to have accessibility descriptions for them in the .ui file they are loaded from. Normally they are created on demand when interacted with, but in this case already exist before that. Seeing as the bogus "formatting mark" is gone I'll call this fixed.