Steps: 1) Open Writer with screen reader active 2) Press F6 until you read the sidebar 3) Press the down arrow until it reaches the Properties tab bar button Tested in LO 5.3 alpha 1, Orca 3.20.3 on Ubuntu Mate 16.04.
Repro with 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
** 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, IMO, the current implementation is logical because we move between items that have to be checked to produce effect. I'm not sure we could make a better implementation. @VStuart: What is your opinion ? Best regards.
(In reply to Alex ARNAUD from comment #3) > Hello all, > > IMO, the current implementation is logical because we move between items > that have to be checked to produce effect. I'm not sure we could make a > better implementation. > > @VStuart: What is your opinion ? > > Best regards. Believe for instrumenting the sidebar/TabBar.cxx buttons in CreateTabItem, the other alternative could be the generic ROLE_SYSTEM_PUSHBUTTON and STATE_SYSTEM_PRESSED pair of a VclPtr<Pushbutton>, rather than the <RadioButton> as used now. But probably more to doing the deck selections as pushbutton than just changing the button object type. =-ref-= https://opengrok.libreoffice.org/xref/core/sfx2/source/sidebar/TabBar.cxx#269
> Believe for instrumenting the sidebar/TabBar.cxx buttons in CreateTabItem, > the other alternative could be the generic ROLE_SYSTEM_PUSHBUTTON and > STATE_SYSTEM_PRESSED pair of a VclPtr<Pushbutton>, rather than the > <RadioButton> as used now. Right, it makes sense to me. I agree with this approach. Best regards.
I can confirm with version 6.3.0.0.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 Calc: threaded
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 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