Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

braille: Can't route to position after last char for TextInfos with no line ending chars #2096

nvaccessAuto opened this issue Feb 9, 2012 · 2 comments


None yet
2 participants
Copy link

commented Feb 9, 2012

Reported by jteh on 2012-02-09 03:17

  1. Focus on a single line editable text field in Firefox.
  2. Type some text.
  3. Press left arrow to move to the last character.
  4. On the braille display, press the routing button for the space after the last character (as if you want to append text to the field).
  5. Expected: The cursor should move to that position.
  6. Actual: The cursor moves to the start of the field.

This happens because you can't move with UNIT_CHARACTER to this position, which is what routing does. This would be fixed if we had a UNIT_OFFSET (which falls back to UNIT_CHARACTER where that isn't possible).


This comment has been minimized.

Copy link

commented Feb 10, 2012

Comment 1 by jteh on 2012-02-10 09:10
Milestone changed from near-term to 2012.1


This comment has been minimized.

Copy link

commented Feb 13, 2012

Comment 2 by jteh on 2012-02-13 02:29
Actually, UNIT_OFFSET doesn't solve this problem, as !OffsetsTextInfo.move limits to text length.

Fixed in 792074e.
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.