Steps to reproduce:
1. Have a text in Writer with 2 paragraphs
2. Put text cursor in the first one of them
3. Switch VoiceOver on (Cmd+F5), notice it focuses on the paragraph with keyboard focus (= first paragraph)
4. Move VoiceOver cursor to the next paragraph (VO-right arrow)
Keyboard focus moves to the next (second) paragraph
Keyboard focus stays at the current (first) paragraph
Tested on OS X 10.8.4 with LO 4.2 master (specifically 39a78087890fb9255a5e47220bac6cfb956fcfe0).
Ideally all the paragraphs would form a single virtual text area using AXSharedTextUIElements, but that's another story for a time when more serious bugs will be fixed.
Can not reproduce with OSX 10.10.1 and LO 4341
Switching paragraphs down via Cmd-Option-Down arrow works and reads out text paragraph
setting as wfm
(In reply to Alex Thurgood from comment #1)
> Can not reproduce with OSX 10.10.1 and LO 4341
> Switching paragraphs down via Cmd-Option-Down arrow works and reads out text
By "can not reproduce", do you mean that when doing "Steps to reproduce" 1.-5. exactly as I described them, you get the "Expected results" and no longer the "Actual results"?
Unless that is the case, this bug cannot be closed, because no matter if you find another way to switch paragraphs (like Cmd-Option-arrow down), moving VoiceOver cursor from one paragraph object to another must move also the keyboard focus with it, as described in "Expected results".
Ah, opk, I misunderstood, sorry about that, I thought it was just about VoiceOver reading out the correct paragraph with the keyboard command switch. Confirming.
Migrating Whiteboard tags to Keywords: (a11y -> accessibility)
** 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.1.6 or 5.2.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)
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!