Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Routing does not work as expected when braille display is tethered to review #2386

nvaccessAuto opened this Issue May 25, 2012 · 5 comments


None yet
2 participants

Reported by aliminator on 2012-05-25 13:17
When a braille display is tethered to review the routing keys do not work.
Following two scenarios should clarify this:

  1. In Notepad, writing some text and changing the cursor position using routing keys seems to bring the braille cursor to its new location.
    But, when arrow keys are used afterwards the cursor is located at its origin position. A routing never did happen in this case.
  2. Using routing keys to execute a left mouse click e. g. in the folder settings dialogue (control panel).
    The option to change is located at the first tab ("show all folders").
    The checkbox is clicked using the routing key. Nothing happens in this case.
    Similar behaviours can be observed in other dialogues or control types.

Comment 1 by jteh on 2012-05-26 04:51
When you're tethered to review, routing keys move the review cursor. Routing keys only move the focus or caret if you're tethered to focus.
Added labels: worksforme
State: closed

Comment 2 by aliminator (in reply to comment 1) on 2012-05-29 10:00
Replying to jteh:
Allowing object navigation in both modes (tethered to focus and review) should be possible due to the fact that there are users using braille output /navigation only. For those speech does not play an important role.
However, currently there is no way to navigate and trigger actions using the braille display only.
When the display is tethered to focus it shows the same text when using object navigation.
When the display is tethered to review navigating objects is fine but no action can be executed because routing keys are not supported in that way.
Hence, the principle described in comment:1 should be modified accordingly.

Comment 3 by jteh on 2012-05-31 11:38
When in a text control, routing should move the review cursor if tethered to review. However, it probably makes sense for routing keys to activate the object when it isn't a text control.
Removed labels: worksforme
State: reopened

Comment 4 by jteh on 2012-05-31 11:39
Milestone changed from None to 2012.3

Comment 5 by jteh on 2012-06-07 08:28
Done in 069209f.
State: closed

@nvaccessAuto nvaccessAuto added this to the 2012.3 milestone Nov 10, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment