Mouse clicking, holding down, dragging, and then releasing on the search engine settings' drop-down menu no longer selects a search engine
Categories
(Firefox :: Settings UI, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox147 | --- | wontfix |
| firefox148 | --- | wontfix |
| firefox149 | --- | wontfix |
| firefox150 | --- | wontfix |
People
(Reporter: cpeterson, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
1.09 MB,
video/mp4
|
Details |
Stephanie, this bug is a regression from bug 1972068. I bisected this regression to this autoland push:
Steps to reproduce
- Open search settings:
about:preferences#search - Click and hold down the mouse button on the search engine drop-down menu.
- Drag the mouse pointer down to highlight other search engines in the drop-down menu.
- Release the mouse button on a different search engine to select it.
Expected result
The new search engine should be selected and the drop-down menu should close.
Actual result
Nothing happens. The new search engine isn't selected. The drop-down menu doesn't close.
See the attached recording.
Updated•9 months ago
|
Comment 1•9 months ago
|
||
:scunnane, since you are the author of the regressor, bug 1972068, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 2•9 months ago
•
|
||
Chris, thanks very much for finding and reporting this bug.
I'm also noticing different behavior on different platforms. (I run Windows 11 and use WSL2 for my dev environment, so I haven't been able to check this on a Mac.)
Windows: after clicking on the moz-select, panel list doesn't display until after the mouseup event
Linux: when clicking on the moz-select, panel list displays with the mousedown event (as in the recording above)
Updated•9 months ago
|
Comment 3•9 months ago
|
||
Just spoke with Tim Giles about this bug. The moz-select behavior changes between patch D279326 and patch D282066, which are part of the same stack. We decided not to back out that entire 5-patch stack because we're close to the end of the dev cycle, this isn't a particularly serious bug, and there is a workaround.
But the incorrect behavior where after clicking on the moz-select, the panel list doesn't display until after the mouseup event was present even before this stack landed.
Tim is currently working on Bug 2017668, which may end up being related to the current bug.
Updated•9 months ago
|
Comment 4•8 months ago
|
||
Set release status flags based on info from the regressing bug 1972068
Comment 5•8 months ago
|
||
Picking the investigation of this bug back up. Tim just landed a fix for bug 2017668, but that seems to not have fixed the current bug.
Updated•8 months ago
|
Comment 6•7 months ago
|
||
After discussing this with Mark Striemer, we've decided that this fix would be more of a nice to have. There will be future work on the moz-select component in the coming months which will fix this issue. But for the time being, this is less of a priority.
Updated•7 months ago
|
Comment 7•4 months ago
•
|
||
I'm no longer able to repro this bug on either Windows or Linux.
Comment 8•4 months ago
|
||
Used mozregression to confirm this was fixed by bug 2026264
Description
•