Steps: 1) Open Writer with NVDA screen reader running 2) Press F6 three times and the screen reader will say 'Option pane' 3) Press arrow keys or tab does nothing This option pane is reachable with other screen readers (JAWS, Orca), but they wont say anything when you land on it, but the real question is what is this pane and why is focus reaching it.
*** Bug 100434 has been marked as a duplicate of this bug. ***
Confirming this behavior with Orca and NVDA on Master.
It's the infobar.
Is there currently an alternative way to access the Infobar with a11y or is this not implemented yet?
(In reply to Maxim Monastirsky from comment #3) > It's the infobar. Thanks. Silly that its getting focus when its not visible. :D
It appears that this one has been identified as being the Infobar. Would a bisect on this one still be useful or is it a waste of time?
(In reply to am_dxer from comment #6) > It appears that this one has been identified as being the Infobar. Would a > bisect on this one still be useful or is it a waste of time? If the problem wasn't present in earlier release it is useful. Best regards.
(In reply to Alex ARNAUD from comment #7) > If the problem wasn't present in earlier release it is useful. Bibisect would only tell us when the infobar was implemented, from my tests its 4.0, so not very useful.
** 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
Hello all I can reproduce this on LibreOffice 6.2 daily build o
...of the 2018-06-12. I'm testing on Debian GNU/Linux 9 "Stretch". Best regards, Alex.
Dear Yousuf Philips (jay) (retired), 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
Hi All, Here is an offering for this that skips the Infobar on F6 when it is not shown: https://gerrit.libreoffice.org/#/c/83636/
Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/0ab044a4798d9968c303e5616f4a307cab0fd62d tdf#105518 F6: Skip infobar when it has no children It will be available in 6.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Verified... Version: 6.5.0.0.alpha0+ (x64) Build ID: 209fc9fd7fa433947af0bf86e210d73fa7f5a045 CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded Still have these substantial issues affecting keyboard AT support and a111y: bug 109425 - for no accessible events being fired while in the NB bug 107343 - for F10 use (or how to handle the Main menu when hidden) bug 127488 - for no accelerator actions (on Windows at least) in the NB
*** Bug 98968 has been marked as a duplicate of this bug. ***