Libreoffice reports bogus indexes to the accessibility stack when the print dialog gets opened, making Orca lost in the dialog box.
Steps to Reproduce:
1) Open LibreOffice Writer
2) Press ctrl+p to open the Print dialog
Orca announces only "print frame"
Orca should announce where it is precisely (Range and Copies panel, Number of copies Text), which would happen fine if indexes were right.
User Profile Reset: No
What Joanmarie found is that when Orca looks a the newly-opened print dialog, the activated field ("number of copies") returns a bogus -1 as index in parent. Looking at it a bit later, the index is correct (1). So I guess there is some kind of race between the notification of the new dialog and widgets, and the actual complete construction of the dialog box.
I tried to remove in vcl/source/window/printdlg.cxx's PrintDialog::PrintDialog the following lines:
maJobPage.mpCopyCountField->SetSelection( Selection(0, 0xFFFF) );
and replace with <property name="has_focus">True</property> in vcl/uiconfig/ui/printdialog.ui to keep the "focus on open" behavior, but the issue in Orca remains the same, so I guess the problem is deeper than just that.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
NEW per Joanmarie being involved.
** 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!
It is still an issue with LibreOffice 18.104.22.168