Closed
Bug 1858978
Opened 2 years ago
Closed 2 years ago
Same search terms across different engines are using the same moz_historyform
Categories
(Firefox :: Address Bar, defect)
Tracking
()
VERIFIED
FIXED
120 Branch
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox118 | --- | unaffected |
firefox119 | --- | unaffected |
firefox120 | --- | verified |
People
(Reporter: aflorinescu, Assigned: daleharvey)
References
(Blocks 1 open bug)
Details
(Whiteboard: [sng-scrubbed])
Attachments
(1 file)
Notes
- While investigating this issue, we figured that for the same search terms queries spread across different engines have the same moz_historyform id, which in turn doesn’t allow deleting and will trigger a not so recent search term pop-up while using a different engine than the one that last_used was updated on.
- To our assessment, this issue and its implications, although it is a S3 from the browser perspective, it can be considered S1/S2 from the feature perspective.
Found in
- Nightly 120.0a1;
Affected versions
- Nightly 120.0a1;
Tested platforms
- Windows 10;
- Ubuntu 22;
- macOS 13;
Preconditions
- browser.urlbar.recentsearches.featureGate set to true
- browser.urlbar.suggest.recentsearches set to true
Steps to reproduce
- Launch Firefox with the profile from preconditions.
- Focus the Address Bar and perform some searches(1,2,3,4,5) using the default search engine(A).
- Change the default search engine and perform the same search using the new default engine(B) (1,2,3,4,5).
- Open a new tab and focus the Address Bar.
- Open the result menu and click on the ‘Remove from history’ option for the (3) of the recent search terms- recent search (3) for engineB is deleted
- Switch back to the original search engine(A) and focus the Address Bar
Expected result
- Recent Search (3) is still displayed for the engine A
Actual result
- Recent Search (3) is not displayed for the engine A.
Regression range
- Not a regression.
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
Updated•2 years ago
|
Whiteboard: [sng-scrubbed]
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
Pushed by dharvey@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bb15479a0d0d
Restrict search history deletions by engine. r=mak
Comment 4•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 120 Branch
Reporter | ||
Comment 5•2 years ago
•
|
||
Verified with 120.0a1 20231018094117 on Windows 10.
Thank you Dale for the fix. With the fix applied, deleting the recent searches works engine base, however the problem for update remains the same. Since we have a patch here, I'm going to open a followup bug - see bug 1859785.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•