Closed Bug 1686314 Opened 2 years ago Closed 2 years ago

Caret gets stuck on a line when going up with up arrow

Categories

(Core :: Disability Access APIs, defect)

Firefox 86
defect

Tracking

()

RESOLVED MOVED
Tracking Status
firefox86 --- affected

People

(Reporter: foss, Unassigned)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

Hello,

Steps to reproduce:

  1. Open the attached file in Firefox
  2. Press down arrow until going on "Have a good night."
  3. Move up arrow to go on the first line "xxx"

Result:
You're stuck on the third line.

Expected result:
You should move on the second then the first line "xxx".

Note:
I discovered this issue when trying to re-read a mail in Thunderbird and being stuck on a line when going up with the up arrow.

Thanks in advance.

Blocks: texta11y, orca

I can't reproduce this with Gecko caret browsing on Windows. Are you using this with Orca? I believe Orca overrides caret browsing to some extent, so perhaps this is specific to Orca (potentially due to something it's not expecting from Gecko a11y)? Are you able to test without Orca to confirm whether this is specific to caret browsing?

Flags: needinfo?(aarnaud)

(In reply to James Teh [:Jamie] from comment #1)

I can't reproduce this with Gecko caret browsing on Windows. Are you using this with Orca? I believe Orca overrides caret browsing to some extent, so perhaps this is specific to Orca (potentially due to something it's not expecting from Gecko a11y)? Are you able to test without Orca to confirm whether this is specific to caret browsing?

Good point, seems an issue with Orca only.

Joanie, do you confirm this too?

Flags: needinfo?(aarnaud) → needinfo?(jdiggs)

I can reproduce it. Yes. Please file a bug against Orca. Thanks!

Flags: needinfo?(jdiggs)

(In reply to Joanmarie Diggs from comment #3)

I can reproduce it. Yes. Please file a bug against Orca. Thanks!

Done, https://gitlab.gnome.org/GNOME/orca/-/issues/179.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → MOVED
You need to log in before you can comment on or make changes to this bug.