-
Bug
-
Resolution: Fixed
-
P5
-
8u20
-
None
sometimes VO focus starts at the wrong node
For example,
run HelloPopupMenu
start VO (Cmd+F5)
Note the black rectangle is around the text (within the Button). It should be around the button as a whole
It also reports 'text element' instead of 'button'.
Another effect of this problem is that VO+Space won't fire button, as the focus is on the text, which does not have a fire action.
One could still do it by moving up from the text to the button first (VO+Shift+Up), then executing the button (VO+Space).
I don't know why this happens, but I'm pretty confident that could be fixed by ignoring the Text node.
Note that this is very common on our Skin implementation, to have a Node that already has a Title Attribute that has another Node as child (that is internally used for rendering) that also Title.
The classic case is Labeled, whose Skin is a LabeledSkinBase, that has a LabeledText inside.
Here, both Labeled and its child LabeledText, are TEXT container for a11y.
For example,
run HelloPopupMenu
start VO (Cmd+F5)
Note the black rectangle is around the text (within the Button). It should be around the button as a whole
It also reports 'text element' instead of 'button'.
Another effect of this problem is that VO+Space won't fire button, as the focus is on the text, which does not have a fire action.
One could still do it by moving up from the text to the button first (VO+Shift+Up), then executing the button (VO+Space).
I don't know why this happens, but I'm pretty confident that could be fixed by ignoring the Text node.
Note that this is very common on our Skin implementation, to have a Node that already has a Title Attribute that has another Node as child (that is internally used for rendering) that also Title.
The classic case is Labeled, whose Skin is a LabeledSkinBase, that has a LabeledText inside.
Here, both Labeled and its child LabeledText, are TEXT container for a11y.