Make Persisted Search with non-default engines consistent with the behavior of default engines
Categories
(Firefox :: Address Bar, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | unaffected |
| firefox130 | --- | unaffected |
| firefox131 | --- | unaffected |
| firefox132 | --- | wontfix |
| firefox133 | --- | verified |
People
(Reporter: jteow, Assigned: jteow)
References
(Blocks 1 open bug, Regressed 2 open bugs, Regression)
Details
(Keywords: regression, Whiteboard: [sng])
Attachments
(1 file, 2 obsolete files)
- Have Persisted Search Enabled
- Do a search with a non-default engine that is a single page application (e.g. DDG, Qwant)
- On their SERP, click on one of the non-default search tabs (e.g. Images, Maps)
Expected Result
- The terms should no longer persist.
Actual Result
- The search terms persist and the search chiclet still appears.
The reason this happens is because userTypedValue is set when we enter search mode. The existence of userTypedValue then prevents future calls to setURI from entering the code path that would unset the cached search terms.
Updated•1 year ago
|
Comment 1•1 year ago
|
||
Set release status flags based on info from the regressing bug 1913312
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 2•1 year ago
|
||
Depends on D224122
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Set release status flags based on info from the regressing bug 1913312
Updated•1 year ago
|
| Assignee | ||
Comment 4•1 year ago
|
||
| Assignee | ||
Comment 5•1 year ago
•
|
||
Erroneous patch.
Updated•1 year ago
|
Comment 7•1 year ago
|
||
| bugherder | ||
Comment 8•1 year ago
|
||
The patch landed in nightly and beta is affected.
:jteow, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox132towontfix.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 9•1 year ago
|
||
I'm not uplifting it to Firefox 132 because the feature affected is not enabled by default.
Reproducible on a 2024-09-25 Nightly build on Windows 10.
Verified as fixed on Firefox Nightly 133.0a1 on Windows 10, Ubuntu 22, macOS 14.
Description
•