Bug 80543

Summary:	SIDEBAR: Paragraph Property panel keyboard navigation hangs at the horizontalalignment toolbox--when AT has been activated (a11y)
Product:	LibreOffice	Reporter:	V Stuart Foote <vsfoote>
Component:	UI	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	caolan.mcnamara, foss, jaragunde, jean-philippe.mengual, philipz85, vsfoote
Priority:	medium	Keywords:	accessibility
Version:	4.2.0.0.alpha1
Hardware:	Other
OS:	All
See Also:	https://bugs.documentfoundation.org/show_bug.cgi?id=102153
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	103440, 103470

Description V Stuart Foote 2014-06-26 00:56:59 UTC

On Windows 7 sp1, 64-bit en-US
Version: 4.4.0.0.alpha0+
Build ID: bdd87b2acddb2e244569dcc8f228e270614dc59e
TinderBox: Win-x86@39, Branch:master, Time: 2014-06-23_00:37:24

In the Sidebar Properties Paragraph panel With keyboard navigation <TAB> will not advance off of the Alignment horizontal toolbar--e.g. Align left, Centered, Align right and Justified.

However, Shift <TAB> will regress through all toolboxes of the panel.

In the sidebarparagraph.ui it looks like it maybe is hanging up on the hidden (in en-US) writedirection toolbox.

Comment 1 V Stuart Foote 2014-06-26 20:35:20 UTC

Hey, here is another clue.

On Windows 7 sp1, 64-bit en-US
did a fresh /A install of 
Version: 4.4.0.0.alpha0+
Build ID: a532e2bba1a2400925e5930d20ab6fd573171085
TinderBox: Win-x86@39, Branch:master, Time: 2014-06-26_00:23:42

Keyboard navigation with TAB moved forward from the paragraph alignment horizontal toolbox until I enabled an AT (NVDA). After that, even with AT (NVDA) disabled--no forward movement onto the Bullets dropdown.  <Shift>+TAB moves backward off the alignment horizontal and cycles backward all the way around.

If I clear profile, TAB movement is restored--until I again enable AT (NVDA).

So this is only happening when the AT has been activated at least once.

Anyone who can comment on OSX NSAccessibility or a Linux Gnome/Orca?

Comment 2 V Stuart Foote 2014-12-08 19:34:47 UTC

*** Bug 71806 has been marked as a duplicate of this bug. ***

Comment 3 V Stuart Foote 2014-12-08 19:37:27 UTC

Present at least since 4.2.0.0 alpah1, manifests when Assistive Technology support activated.

Comment 4 QA Administrators 2015-12-20 16:15:54 UTC Comment hidden (obsolete)

** 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.0.4 or later)
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

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 your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20

Comment 5 Yousuf Philips (jay) (retired) 2016-09-13 10:47:36 UTC

So the problem seems to occur if you have CTL disabled, which is the default. Just another reason why the buttons should be visible but disabled rather than hidden. :D

Version: 5.3.0.0.alpha0+
Build ID: 78404fe5549fded2eaf0c5ea6e1ca66039e995af
CPU Threads: 2; OS Version: Linux 3.19; UI Render: default; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-09-11_09:14:01
Locale: en-US (en_US.UTF-8); Calc: group

Comment 6 QA Administrators 2017-11-17 09:10:54 UTC Comment hidden (obsolete)

** 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.

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

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

Comment 7 Alex ARNAUD 2017-12-01 13:25:58 UTC

Dear all,

I can reproduce on LibreOfficeDev 6.1 from 2017-11-26.

Best regards.

Comment 8 QA Administrators 2018-12-03 03:59:32 UTC Comment hidden (obsolete)

** 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.

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

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

Comment 9 Alex ARNAUD 2019-01-18 13:56:18 UTC

Dear all,

I cannot reproduce on LibreOfficeDev 6.3 (VCL GTK3) from 2019-01-16 on Debian 9 "Stretch" (GNU/Linux).

I can confirm the original issue with LibreOffice 6.1.4.2 on the same computer with also VCL GTK3.

Best regards,
Alex.