Created attachment 124992 [details]
pyatspi accessible-event listener
Steps to reproduce:
1. Launch LibreOffice Writer within GNOME Shell
2. Launch the attached pyatspi accessible-event listener in a terminal
3. Show the Styles and Formatting panel/frame
4. Arrow up and down within the hierarchical list
Expected results: Only the keyboard events would be output in the terminal.
Actual results: A bunch of children-changed accessibility events coming from gnome-shell are output in between each press and release. (See attached sample output.)
I had originally planned to file this against GNOME Shell. But I went looking for some other application to demonstrate that it wasn't LibreOffice's bug/fault. I so far haven't been able to find one. I'm only seeing the problem in LibreOffice. Then I tried to reproduce the problem using other LibreOffice Writer dialogs. Couldn't reproduce the problem. There is something special about the list of styles. And it would be great if you could figure out what it is and stop it from triggering event floods in GNOME Shell.
Impact: Every time an Orca user changes the selected item in Styles and Formatting, Orca gets hit with a bunch of pointless events. And while it is discarding them quickly, having to examine that many events to be sure they're not of any interest can make Orca feel a bit laggy.
I have tried Writer 126.96.36.199 and 5.2 and am using GNOME Shell 3.20.1 in Fedora 24.
Created attachment 124993 [details]
Sample output performing the steps in the opening report
Version set from description.
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker