Closed Bug 1958766 Opened 11 months ago Closed 9 months ago

Narrator reports the title of the document when moving by word or character out of a link

Categories

(Core :: Disability Access APIs, defect)

defect

Tracking

()

VERIFIED FIXED
141 Branch
Tracking Status
firefox-esr128 --- unaffected
firefox137 --- unaffected
firefox138 --- disabled
firefox139 --- disabled
firefox140 --- disabled
firefox141 --- verified
firefox142 --- verified

People

(Reporter: Jamie, Assigned: Jamie)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Spun off bug 1950535 comment 6.

STR:

  1. Ensure Firefox UIA is enabled: about:config, set accessibility.uia.enable to 2.
  2. Turn on Narrator.
  3. Open: https://example.com/
  4. Press control+end to move to the last line of the document. Narrator should say: "More information"
  5. Press control+leftArrow to move to the previous word.
    • Expected: Narrator should say: "permission"
    • Actual: Narrator says: "Example Domain"

I apparently regressed this in bug 1951573:

8:52.42 INFO: Last good revision: ea634003c48cb1ab307649baf8fb18476a0e14c6
8:52.42 INFO: First bad revision: 23a8b787c70c3a31c483006679653b2cdc13b300
8:52.42 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ea634003c48cb1ab307649baf8fb18476a0e14c6&tochange=23a8b787c70c3a31c483006679653b2cdc13b300

I think the problem is that setting the caret ends up setting the focus to the document, which is apparently problematic for Narrator. 😒 That said, I can't seem to reproduce that outside of Narrator just yet, which is weird.

Set release status flags based on info from the regressing bug 1951573

[Removed accidental comment.]

See Also: → 360003
See Also: 360003

In bug 1951573, I unified the code for setting the caret.
This includes focusing the node at the caret.
Unfortunately, Windows Narrator behaves badly if the focus is changed as a result of setting the caret.
Chromium doesn't move the focus if the caret is moved via UIA, even though it does for caret navigation like Firefox.
ATK in particular still wants the focus to be changed.
Therefore, add an aSetFocus argument to TextLeafRange::SetSelection so this can be configured by the caller.
Change UIA to specify aSetFocus = false.

Regressions: 1970561
No longer regressions: 1970561
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Target Milestone: --- → 141 Branch
QA Whiteboard: [qa-triage-done-c142/b141] [qa-ver-needed-c142/b141]
Flags: qe-verify+
QA Contact: oardelean

Reproducible on a 2025-04-07 Firefox Nightly build on Windows 10.
Verified as fixed on Firefox Nightly 142.0a1 and Firefox 141.0b2 on Windows 10 and Windows 11.

Status: RESOLVED → VERIFIED
QA Whiteboard: [qa-triage-done-c142/b141] [qa-ver-needed-c142/b141] → [qa-triage-done-c142/b141] [qa-ver-done-c142/b141]
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: