Steps to reproduce : - open a document in readonly mode with nvda activated, - move with arrow one line down - nvda still read the first line, - try to move with Ctrl + Arrow to the next paragraph, - after few Ctrl + Arrow, nvda stop reading anything.
On Windows 10 Pro 64-bit with NVDA 2015.1 and Version: 5.0.1.1 (x64) Build ID: 13f702ca819ea5b9f8605782c852d5bb513b3891 Locale: en-US (en_US) With .ODT document set to read only mode (Edit -> Edit mode toggled) can not reproduce. NVDA will sound paragraph by paragraph advancing or regressing with <Ctrl>+DOWN or <Ctrl>+UP respective. There remains issue of bug 91739 where NVDA will not sound entire document with NVDA Key--(default Insert)+DOWN, where sounding will halt as paragraph transitions into an area not displayed in screen buffer. So, could be related to that aspect. However, the <Ctrl>+DOWN or <Ctrl>+UP are functioning correctly with NVDA 2105.1
On Windows 7 64-bit with NVDA 2015.2 I install LO Version: 5.0.1 and I always the bug, it is even worse.
With LO 5.0.1.1 Build ID: 13f702ca819ea5b9f8605782c852d5bb513b3891, Locale : fr-FR (fr_FR) Windows 7 Home Premium, NVDA 2015.2 file previously set to readonly mode, I observe the same behavior than irina. Ctrl+UP, instead of DOWN, give however reading of the whole paragraph.
Migrating Whiteboard tags to Keywords: (a11y -> accessibility)
*** Bug 97255 has been marked as a duplicate of this bug. ***
Created attachment 124375 [details] test document with numbered dummytext AutoText for navigation On Windows 8.1 Ent 64-bit en-US with with NVDA 2016.1 and Version: 5.1.2.2 (x64) Build ID: d3bf12ecb743fc0d20e0be0c58ca359301eb705f CPU Threads: 8; OS Version: Windows 6.29; UI Render: default; Locale: en-US (en_US) Read-only mode navigation, either Say-all or by paragraph <ctrl>+Down/Up sounds correctly. Continue to be unable to reproduce.
Hi, Is there a difference between portable release ;5.0.5) and others? I tested today on Portable release 5.0.5, Windows P i386, NVDA 2016.1. I still reproduce. Regards,
** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
(In reply to V Stuart Foote from comment #6) > Created attachment 124375 [details] > test document with numbered dummytext AutoText for navigation > > On Windows 8.1 Ent 64-bit en-US with > > with NVDA 2016.1 and > > Version: 5.1.2.2 (x64) > Build ID: d3bf12ecb743fc0d20e0be0c58ca359301eb705f > CPU Threads: 8; OS Version: Windows 6.29; UI Render: default; > Locale: en-US (en_US) > > Read-only mode navigation, either Say-all or by paragraph <ctrl>+Down/Up > sounds correctly. > > Continue to be unable to reproduce. hello. i still can reproduce the bug in recent versions of libreoffice and also nvda. my issue is even worse. i write in one separate comment. God bless you.
hello. i tested my books with libreoffice versions 4.4, 5.0 and 5.1 and also 5.2 in 4.4 and 5.0 as i remember, i could not use arrow keys to navigate in my books in readonly mode. in 5.1 sometimes arrow keys work and sometimes not. in the versions that i could not use arrow keys, nvda became completely silent and only read the title of book with readonly libreoffice writer and nothing other. i tested with 5.2.6 and also 5.2.7 and the issue is completely resolved for me! i can use arrow keys and different keys to read my books. thanks extremely for your great job! i sincerely pray for you in my five times obligatory prayers and request divine infinite mercy and blessings for you!