Text selection handles are not displayed on Nightly.
Categories
(Fenix :: General, defect, P1)
Tracking
(firefox115 unaffected, firefox116 unaffected, firefox117+ fixed)
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.
Comment 2•1 year ago
|
||
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!
Updated•1 year ago
|
Updated•1 year ago
|
Comment 3•1 year ago
|
||
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)?
Comment 5•1 year ago
|
||
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.
Updated•1 year ago
|
Comment 6•1 year ago
|
||
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.
Comment 7•1 year ago
|
||
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.)
Updated•1 year ago
|
Comment 8•1 year ago
|
||
I am able to use mozregression to reproduce this and that leads to https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=87f35bfe2247c1dface09d2c1f0f9c6ec6ab2bfa&tochange=60d4eb46c8b40ab0cd000c9ef298c63c45539be7, which is Emilio's patch.
Assignee | ||
Comment 9•1 year ago
|
||
I can repro on my device (but not on desktop as Ting-Yu mentioned, which is weird). Checking.
Assignee | ||
Comment 10•1 year ago
|
||
We need these to be contentaccessible. Let's make sure they use the same
set-up as desktop's images.
Assignee | ||
Comment 11•1 year ago
|
||
The less useless files the better.
Depends on D183293
Assignee | ||
Updated•1 year ago
|
Comment 12•1 year ago
|
||
Comment 13•1 year ago
|
||
Comment 14•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/ae1b606076e2
https://hg.mozilla.org/mozilla-central/rev/09e607211b8c
Description
•