When composing a document, and the user wishes to add a comment, once you press the Control+Alt+C keybinding to add a comment to a highlighted portion of text, or to a area of text that is proceeding the cursor, Orca does not interact with the comment field. Arrowing through the text typed out provides no speech output. Deleting text does not provide speech output.
Activating the menu item under Insert, Comment, yields the same result.
Using the Control + Alt + Page Up and Page Down functions to cycle through comments only reads the text written out for that particular area that is commented, does not allow navigation to the actual comment itself with orca.
Perhaps provide a keybinding that will get to the list of comments presented should there already be some?
Migrating Whiteboard tags to Keywords: (a11y -> accessibility)
I can confirm with Version: 18.104.22.168.alpha1+
Build ID: eb7593daa4bac21bd68182c8bbbd3ee3bd7b64dd
CPU Threads: 4; OS Version: Linux 4.4; UI Render: default;
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-05-03_07:06:45
with the latest Orca (3.20.2) and latest LibrOffice fresh (5.1.4) the problem continues to appear.
*** Bug 101002 has been marked as a duplicate of this bug. ***
Confirmed with 5.2.1 on windows with NVDA.
This issue still exsits in LibreOffice 22.214.171.124 (x64) using NVDA 2017.3.
Issue on NVDA issue tracker: https://github.com/nvaccess/nvda/issues/7700
** 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!
I can confirm with version 126.96.36.199.alpha0+
Build ID: 4187b2beaa3d1294cd5c76ec0b662f3f4fadc421
Threads CPU : 12; OS : Linux 4.19; UI Render : par défaut; VCL: gtk3;
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-02-25_07:04:36
Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR