Description: When navigating the Find dialog, with Tab and Shift+Tab some items are not spoken and focus is not predictable. Steps to Reproduce: 1. Press Control+f to open the Find dialog. 2. Tab 6 times to the Navigate by button. 3. Press the Tab key again and nothing is spoken. 4. Press Shift+Tab, focus jumps back to the Close Find Bar button. Actual Results: Keyboard focus is unpredictable and some items are not spoken. Expected Results: Keyboard focus should move sequentially through controls and all should be correctly spoken. Reproducible: Always User Profile Reset: Yes Additional Info: Tested with NVDA on Windows User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
(In reply to am_dxer from comment #0) > Description: > When navigating the Find dialog, with Tab and Shift+Tab some items are not > spoken and focus is not predictable. > > Steps to Reproduce: > 1. Press Control+f to open the Find dialog. > 2. Tab 6 times to the Navigate by button. > 3. Press the Tab key again and nothing is spoken. > 4. Press Shift+Tab, focus jumps back to the Close Find Bar button. I get a different result. For step 3., it is spoken. Shift+Tab then jumps back to Navigate by. Used NVDA. Win 7 Pro 64-bit Version: 5.4.0.0.alpha0+ Build ID: c6dd735afb2e1b3837c4f8c5659f52fafab4c56f CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-01-30_01:52:54 Locale: fi-FI (fi_FI); Calc: group
The order of the Find dialog has changed since I filed this bug so it now requires slightly different steps to reproduce. 1. Once in the Find dialog, tab 8 times to the Next Element button. 2. Press Tab again and NVDA is silent. 3. Press Shift+Tab and NVDA's focus lands on the Close Find Bar button. Version: 5.4.0.0.alpha0+ Build ID: a296a69c984b17cfbcd249cf6bdc191d08dff2a6 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-02-06_00:00:55 Locale: en-US (en_US); Calc: group
Repro. Win 7 Pro 64-bit Version: 5.4.0.0.alpha0+ Build ID: 83e059af2203ec0cd15dea08cfa538555ba14bd7 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-02-06_23:34:43 Locale: fi-FI (fi_FI); Calc: group
Can't repro this one in an old OpenOffice. I will try to bisect it.
I can reproduce this in 5.0.0.2. Must be older.
Repro in 4.3.0.1. Must be older.
Repro in 3.5.7.2. Must be older.
(In reply to am_dxer from comment #4) > Can't repro this one in an old OpenOffice. I will try to bisect it. Which version are you talking about ? Best regards.
hello. i confirm this problem in libreoffice 5.3.4.1 and i had this issue since libreoffice 4.3.0 which was the first accessible version of libreoffice without need installing java and java access briedge. i tested find dialog in openoffice and had not this issue. i tested openoffice 4.1.0 until 4.1.3 i use windows xp with nvda 2017.2
** 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 bug on LibreOffice version 6.1.5.1 (gtk3; )
Dear am_dxer, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
(In reply to Patrick ZAJDA from comment #11) > I can reproduce this bug on LibreOffice version 6.1.5.1 (gtk3; ) I can't reproduce using comment 2 steps with Orca + LO 5.4.0.3, nor 6.1.0.3, nor a recent master build at 24.2 alpha0+. Let's keep this as Windows + NVDA-only for now, but Michael, can you please check if this is still relevant? Thank you!
(In reply to Stéphane Guillou (stragu) from comment #13) > I can't reproduce using comment 2 steps with Orca + LO 5.4.0.3, nor 6.1.0.3, > nor a recent master build at 24.2 alpha0+. Let's keep this as Windows + > NVDA-only for now, but Michael, can you please check if this is still > relevant? > Thank you! I can't reproduce on Windows 10 with NVDA 2023.2 and a current LO development version either. Tab order is as expected and each focused element is announced. -> closing as worksforme @am_dxer: Could you please retest as well whether everything works as expected in your setup as well now? Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 36163d269bd8f77a86605e4c5ff5adce17b4c66c CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_DE); UI: en-US Calc: threaded