Closed
Bug 1838010
Opened 2 years ago
Closed 2 years ago
Separator & spacing for "Search with" in case of google rich entities spacing depending on description
Categories
(Firefox :: Address Bar, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1841408
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox114 | --- | disabled |
| firefox115 | --- | wontfix |
| firefox116 | --- | fixed |
People
(Reporter: aflorinescu, Assigned: daleharvey)
References
(Blocks 3 open bugs)
Details
Attachments
(1 file, 1 obsolete file)
|
141.47 KB,
image/jpeg
|
Details |
Found in
- 115.0b4
Affected versions
- 115.0b4
- 116.0a1 116.0a1 (2023-06-11)
Tested platforms
- Affected platforms:
- Windows 10
- Mac 11.7.4
- Ubuntu 22.04
Preconditions
- Google as default search engine.
*browser.urlbar.richSuggestions.featureGate set to true
Steps to reproduce
- Open Firefox
- Run the following snippet in the Browser Console:
Services.prefs.getDefaultBranch("").setCharPref("browser.search.param.search_rich_suggestions", "fen") - Type in address bar a query that will return rich entities with long description
- Hoves over the search suggestion that has a long description
Expected result
The separator + spacing betwen the search suggestion and "Search with engine" stays the same
Actual result
The separator + spacing betwen the search suggestion and "Search with engine" varies depending on the rich entity description (see #attachement)
Regression range
- N/A
Notes
- The description needs to be longer than
search suggestion+space+separator+space+Search with engine
Comment 1•2 years ago
|
||
:aflorinescu, if you think that's a regression, could you try to find a regression range using for example mozregression?
| Assignee | ||
Updated•2 years ago
|
Assignee: nobody → dharvey
| Assignee | ||
Comment 2•2 years ago
|
||
Updated•2 years ago
|
Attachment #9341503 -
Attachment is obsolete: true
| Assignee | ||
Comment 3•2 years ago
|
||
The layout is being redone in the duped bug and will no longer be relevant
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•