Closed Bug 1934489 Opened 3 months ago Closed 3 months ago

[A11y] Touch exploration with TalkBack stops working after zooming the page on Android

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Version:
Firefox 135
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
135 Branch
Tracking Flags:
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- wontfix
firefox133 --- wontfix
firefox134 + wontfix
firefox135 + fixed

People

(Reporter: BlindMoon38, Assigned: eeejay)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Bug 1934489 - P1: Update ScrollPosition cache when "scrollable" element has no scrollable frame. r?morgan
48 bytes, text/x-phabricator-request
Details | Review
Bug 1934489 - P2: Update scroll position on CSS overflow change in each axis. r?morgan
48 bytes, text/x-phabricator-request
Details | Review

Steps to reproduce

  • Open Firefox for Android with TalkBack enabled.
  • Go to https://es.m.wikipedia.org/wiki/Euskera.
  • Scroll down the page a little.
  • Pinch to zoom the page.
  • Try using touch exploration to explore the content of the page.

Expected results

Using Touch exploration, It should be possible to focus elements while the page is zoomed in.

Actual results

It's not possible to focus any elementsusing touch exploration while the page is zoomed in.

Firefox version

  • Firefox Nightly from 2024-11-29T00:34:09.497018301.
  • 135.0a1 (Build #2016058887), hg-dd2ffa8af894+.
  • GV: 135.0a1-20241128215411.
  • AS: 135.20241128050339.

Device

  • Xiaomi Poco X6 5G with HyperOS 1.0.17.0 based on Android 14.

Additional information

  • TalkBack version 15.1.
  • Thebug is harder to reproduce if you don't scrollddown the page before zooming in.

Triaging as s2 for now, since this impacts the ability to explore the screen. In theory, bug 1899658 should have fixed this, but I guess it hasn't in this instance.

Eitan, would you mind looking into this when you get a chance? Thanks.

Severity: -- → S2
Component: Disability Access → Disability Access APIs
Depends on: 1899658
Flags: needinfo?(eitan)
Product: Firefox → Core
Blocks: boundsa11y

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Status: UNCONFIRMED → NEW
Ever confirmed: true

The bug is marked as tracked for firefox134 (beta) and tracked for firefox135 (nightly). However, the bug still isn't assigned.

:fgriffith, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Flags: needinfo?(fgriffith)
Assignee: nobody → eitan
Flags: needinfo?(fgriffith)

A document's body element can lose its scroll frame if the root element (eg. <html>) is restyled to overflow scroll/auto. In that case we will not get any useful notifications for the body element except for a reframe to a non-scrolling frame.

The place where we see this as a problem is in hit testing because
accessibles get erroneously clipped out because of stale scroll
positions.

Tried really hard to generalize the failing case further, but it looks like this is related to how the root scroll frame works.

Flags: needinfo?(eitan)
Attachment #9442983 - Attachment description: Bug 1934489 - Update ScrollPosition cache when "scrollable" element has no scrollable frame. r?morgan → Bug 1934489 - P1: Update ScrollPosition cache when "scrollable" element has no scrollable frame. r?morgan

The way the code was written it would expect a uniform overflow style
for both x and y. We need to make sure to handle each axis separately.

Pushed by eisaacson@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b1c9cdccd0dd P1: Update ScrollPosition cache when "scrollable" element has no scrollable frame. r=morgan https://hg.mozilla.org/integration/autoland/rev/a7b9142fd957 P2: Update scroll position on CSS overflow change in each axis. r=morgan

https://hg.mozilla.org/mozilla-central/rev/b1c9cdccd0dd
https://hg.mozilla.org/mozilla-central/rev/a7b9142fd957

Status: NEW → RESOLVED
Closed: 3 months ago
status-firefox135: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → 135 Branch

The patch landed in nightly and beta is affected.
:eeejay, is this bug important enough to require an uplift?

  • If yes, please nominate the patch for beta approval.
  • If no, please set status-firefox134 to wontfix.

For more information, please visit BugBot documentation.

Flags: needinfo?(eitan)
status-firefox134: affected → wontfix
Flags: needinfo?(eitan)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: