Closed Bug 1842608 Opened 1 year ago Closed 1 year ago

Text selection handles are not displayed on Nightly.

Categories

(Fenix :: General, defect, P1)

Firefox 117
All
Android

Tracking

(firefox115 unaffected, firefox116 unaffected, firefox117+ fixed)

RESOLVED FIXED
117 Branch
Tracking Status
firefox115 --- unaffected
firefox116 --- unaffected
firefox117 + fixed

People

(Reporter: tyotomy, Assigned: emilio)

References

(Regression)

Details

(Keywords: regression, regressionwindow-wanted, Whiteboard: [qa-triaged])

Attachments

(2 files)

User Agent: Mozilla/5.0 (Android 9; Mobile; rv:109.0) Gecko/117.0 Firefox/117.0

Steps to reproduce:

After update to 117.0a1 (Build #2015961379), Text selection handles are not displayed.
However, although it is not actually visible, it exists and you can move the range by selecting it.

Duplicate of this bug: 1842716

Hello,
I was able to reproduce the issue on the latest Nightly build (117.0a1) from 11th of July 2023. The issue is only reproducible in the Nightly build, Beta and RC are not affected.
Devices used for testing: Google Pixel 7 Pro (Android 13), Lenovo Tab P11 Plus (Android 12).
Thank you!

Severity: -- → S3
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [qa-triaged]

Hard to get a definitive regression range without having an idea of a last-known-good build, but here's a couple days' worth of Gecko commits leading up to the first affected Nightly build:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e4d87ff75575&tochange=76990d265adf8f3e06e2352d422a410ae6c899a0

Is this reproducible with GVE (and bisectable with mozregression)?

Offhand, bug 1817723 looks maybe related?

Flags: needinfo?(sefeng)

mozregression doesn't work ATM on GVE, see https://bugzilla.mozilla.org/show_bug.cgi?id=1835067. But we'll try to get the first bad build if possible.

Please use mozregression 5.4.1.dev1 for the time being until the next version is released. This dev version has a workaround that will allow you to run GVE.

I cannot reprduce on desktop Nightly with layout.accessiblecaret.enabled=true and layout.accessiblecaret.hide_carets_for_mouse_input=false. I don't have a Android device to reproduce at hand.

In the regression range in comment 3, bug 1824886 contains a refactor to AccessibleCaret's internal display mechanism.

Emilio, could you take a look if your patches cause this? (Change Severity to S1 because AccessibleCaret is missing on mobile device.)

Severity: S3 → S1
Flags: needinfo?(emilio)
Priority: -- → P1
Flags: needinfo?(sefeng)
Keywords: regression
Regressed by: 1824886

I can repro on my device (but not on desktop as Ting-Yu mentioned, which is weird). Checking.

Assignee: nobody → emilio

We need these to be contentaccessible. Let's make sure they use the same
set-up as desktop's images.

The less useless files the better.

Depends on D183293

Flags: needinfo?(emilio)
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ae1b606076e2 Move Android's accessiblecaret SVG's to layout/style/res. r=TYLin,geckoview-reviewers,owlish
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/09e607211b8c Don't ship accessiblecaret's desktop pngs on mobile. r=TYLin
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: