1068884 - [Camera] Option selections in menu are not operable

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::Camera, defect)

Description

[Eitan Isaacson [:eeejay]]

STR:
 1. Go to menu.
 2. Press Self-Timer
 3. Try selecting options in menu with screen reader

Result: Can't!

Comment 1

[GitHub Autolander Bot]

Attachment: [gaia] FunkTron:Bug1068884 > mozilla-b2g:master

Comment 2

[Ross]

The PR introduces a preliminary fix to the issues highlighted in the bug's description, but incidentally may have revealed another bug (and/or further necessary work for this bug) that should be addressed before this issue as a whole can be considered resolved.  After installing the patch, the new functionality is as follows:

1. Go to menu.
2. Press Self-Timer
3. Try selecting and/or activating options in menu with screen reader (WORKS!)
4. After activation, the virtual cursor remains on the screen in the same position despite the menu and all options having been destroyed in the DOM

Investigation of logcat while performing the operations above seems to reveal that a "HIDE Event" is triggered, and that this.contentControl.autoMove() is called, but the call to autoMove() simply returns without doing anything.  Specifically, the autoMove() logic progresses to https://dxr.mozilla.org/mozilla-central/source/accessible/jsat/ContentControl.jsm#486, then returns after failing the IF statement in https://dxr.mozilla.org/mozilla-central/source/accessible/jsat/ContentControl.jsm#442

Not sure if we should just be looking to manually set the focus after the settings menu closes here (to properly reset the VC) or if we should be investigating the vc.moveNext() method and/or traversal rules, or possibly investigating the way the menus are removed from the DOM and adjusting them so that they play more nicely with the screen reader.

Comment 3

[Yura Zenevich [:yzen] (please use "needinfo")]

Sorry, didn't realize there was this bug, this one is fixed with bug 1068880

Comment 4

[Eitan Isaacson [:eeejay]]

As we investigated, this issue is because there are two subsequent dialogs. So the previous position before the second dialog is in the first dialog that is already gone. Thus, the vc does not automove anywhere. Ideally, with this kind of extreme case, we should at least land on the first item in the app, if not anything else.