Search engine icons are cut off
Categories
(Firefox :: Search, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox106 | --- | unaffected |
| firefox107 | --- | disabled |
| firefox108 | --- | verified |
People
(Reporter: alice0775, Assigned: emilio)
References
(Regression)
Details
(Keywords: nightly-community, regression)
Attachments
(2 files)
screencast
Steps to reproduce:
- Install a lot of search engine
- Enable Standalone Search bar
- Click Magnifying glass in Standalone Search bar
Actual results:
Search engine icons are cut off. See attached screenshot.
Expected Results:
All icons should be visible.
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=48c266f64c004b63ce578243d3e5a82c9540e308&tochange=fb32775d2defaa2fe7d6e270aefc31d80b3f729a
|
Assignee | |
Updated•2 years ago
|
|
|
Assignee | |
Comment 1•2 years ago
|
||
The interaction of legacy flexbox (menupopup) with block is a bit nicer
than with flex.
I'm going to update menupopup with modern flexbox as soon as I fix all
the browser-chrome tests and the soft freeze is over, but this is
harmless and fixes the bug both with and without modern flexbox.
Remove -moz-box-flex: 0; from search-panel-tree since it's now useless
(there's no flexing to do since parent isn't a flex container).
|
||
Comment 2•2 years ago
|
||
Set 107 to disabled, regressor bug 1790616 backed out of central
|
||
Updated•2 years ago
|
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7f762ef403e2 Use `display: block` for search autocomplete popup. r=dao
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
|
||
Comment 5•2 years ago
|
||
I am unable to reproduce the issue on the mentioned build (Fx 107.0a1). The issue also doesn't occur for me in the latest Fx 108.0a1 on Windows 10 (on a 1440p monitor, if it matters).
Alice, could you please help us with a confirmation here that the issue has been fixed?
|
Reporter | |
Comment 6•2 years ago
|
||
I managed to reproduce this issue in Nightly107.0a1(20221014095137).
And I can confirm that the issue is no longer reproduced in Nightly108.0a1(20221026224258) and Firefox106.0b5.
Description
•