1950754 - Windows Text Cursor Indicator is off by one in Google Search results page text box

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[Nathan LaPré]

STR:

1. Turn on UIA support in about:config; set accessibility.uia.enable to true.
2. Turn on the Windows Text Cursor Indicator (Settings -> Accessibility -> Text Cursor -> Set Text cursor indicator to "On")
3. Search for anything on Google, maybe search term "ABCDEF"
4. On the results page, focus the search input at the top of the page by clicking in the empty space to the right of the "F" in the search term.
5. Observe the location of the Windows Text Cursor

Expected: Text cursor indicator appears where the input cursor is: after the F.
Actual: Text cursor indicator is after the E and before the F.

This works in Edge. It's also broken (worse) using the IA2 -> UIA bridge in Firefox. If you click again in the same spot, the text cursor indicator snaps to the right location. Similarly, if you start keyboard navigating through the input, the text cursor indicator will snap to the right location.

This seems a lot like the bug report in Bug 1950740, but I'm not sure it's the same issue. I wasn't able to reproduce the behavior described here in a reduced testcase, despite some attempts. I also wasn't able to reproduce the behavior in a simple handwritten <textarea> (which the results page uses). It might be fixed by the fix to Bug 1950740, but I think it's worth capturing here since Google search is such an important site.

Comment 1

[James Teh [:Jamie]]

Morgan, do you mind re-testing this when you get a chance? I'm wondering whether it's been fixed by one of several character bounds fixes recently. No urgency; this isn't a ship blocker.

Comment 2

[Morgan Reschenberg [:morgan]]

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

Morgan, do you mind re-testing this when you get a chance? I'm wondering whether it's been fixed by one of several character bounds fixes recently. No urgency; this isn't a ship blocker.

This is fixed :) I'll leave the bug open since I'm not sure which fix resolved this issue / where to dupe it -- you might have a better idea

Comment 3

[James Teh [:Jamie]]

Thanks Morgan. I'm not exactly sure which patch fixed this bug. It's likely bug 1950740 or bug 1977507.