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

Closed
nvaccessAuto opened this Issue Feb 9, 2012 · 2 comments

2 participants

@nvaccessAuto

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

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

@nvaccessAuto

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

@nvaccessAuto

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.
Changes:
State: closed

@jcsteh jcsteh was assigned by nvaccessAuto Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 2012.1 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment