1511955 - Navigating by character on compound elements yields unpredictable results

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[Marco Zehe (:MarcoZ)]

STR (with TalkBack in Focus or Fennec):
1. Open https://www.heise.de/newsticker
2. Touch any of the news article headings.
3. Swipe up a few times until you reach the Characters granularity.
4. Swipe right a few times.

Expected: TalkBack should read the numbers for each time stamp, the link text, and other information as you move by character.

Actual: TalkBack reads the first digit of the time, then the whole link text, then a space, then something else, and already jumps to the next item below.

5. Swipe to the left a few times.

Expected: TalkBack should traverse in reverse order.
Actual: TalkBack reads some characters from the link, the time, the other text in an element, but nothing consistent.

This all works nicely in Chrome.

Comment 1

[Eitan Isaacson [:eeejay]]

Attachment: Bug 1511955 - Don't traverse into children without hypertext interfaces. r?Jamie!

This prevents an infinite loop where we go into a child only to find the
nearest hypertext accessible being its parent.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/3386ff76878d
Don't traverse into children without hypertext interfaces. r=Jamie

Comment 3

[Arthur Iakab [arthur_iakab]]

https://hg.mozilla.org/mozilla-central/rev/3386ff76878d

Comment 4

[Ryan VanderMeulen [:RyanVM]]

Is this something we should consider uplifting to GV64?

Comment 5

[Chris Peterson [:cpeterson]]

Eitan, should we uplift this fix to the GeckoView 64 release branch?

GeckoView 64 will be rolled out to 10-15% of Focus 8.0 users this week. GeckoView 65 won't be ready for about six weeks, so we might release one or two dot more releases for GeckoView 64.

Comment 6

[Eitan Isaacson [:eeejay]]

Oops, I missed this. I think we could let it slip. It was a bug prior to 64 as well.

Comment 7

[Chris Peterson [:cpeterson]]

(In reply to Eitan Isaacson [:eeejay] from comment #6)
> Oops, I missed this. I think we could let it slip. It was a bug prior to 64
> as well.

SGTM!

64=wontfix