Same search terms across different engines are using the same moz_historyform (update)
Categories
(Firefox :: Address Bar, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox118 | --- | unaffected |
firefox119 | --- | unaffected |
firefox120 | --- | wontfix |
firefox121 | --- | wontfix |
firefox124 | --- | fixed |
People
(Reporter: aflorinescu, Assigned: daleharvey)
References
(Blocks 3 open bugs)
Details
(Whiteboard: [sng])
Attachments
(2 files)
Notes
- Follow-up from bug 1858978
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.
- Have a search done with default engine(A) for
search_term
any time. (e.g. in the past - let's say 2 months ago - below STR cover this scenario, or just recently - for more recent searches, the recent search order will get changed by same search done on different engine) - Focus the Address Bar and perform some searches(x,y,z) using the default search engine(A).
- Focus the Address Bar and notice the Recent Searches.
- Use search shortcut for any engine, but the default engineA - e.g.
@engineB search_term
- Focus the Address Bar and notice the Recent Searches.
- Change default engine to the engineB, focus the Address Bar and notice the Recent Searches.
Expected result
- step 4 - Recent Search display
x
,y
,z
for engine(A) - step6 - Recent Search display
x
,y
,z
for engine(A) - step7 - Recent search display
search_term
for engine(B)
Actual result
- step 4 - Recent Search display
x
,y
,z
for engine(A) - step6 - Recent Search display
x
,y
,z
,search_term
for engine(A) - step7 - Recent search display
search_term
for engine(B)
Regression range
- Not a regression.
Comment 1•8 months ago
|
||
:aflorinescu, if you think that's a regression, could you try to find a regression range using for example mozregression?
Updated•8 months ago
|
Updated•8 months ago
|
Reporter | ||
Comment 2•7 months ago
|
||
As discussed with :dharvey and :hmosety, this is not in scope for 120 experiment, hence will not be fixed for 120 version, marking as such for visibility.
Assignee | ||
Updated•4 months ago
|
Assignee | ||
Comment 4•4 months ago
|
||
Pushed by dharvey@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e2a57589d787 Only show recent searches since last engine change. r=daisuke
Comment 6•4 months ago
|
||
bugherder |
Updated•4 months ago
|
Reporter | ||
Comment 7•4 months ago
|
||
Hey Dale.
Can you please elaborate how this patch affects the functionality for Recent Searches? At first glance, seems like this bug isn't fixed yet(see recording), in addition now not having the historical recent searches done with other engines before the default engine switch.
Assignee | ||
Comment 8•4 months ago
|
||
Hey Adrian, answering here so its easier to look back on.
You are right, for this fix I was concentrating on the situation where the other searches were performed because the user had switched default engines, when the user performs searches with non default engines then it is still possible to have them in an unexpected order.
I will clone this one so we dont get confused about tracking the patch, fixing that situation may end up in a wontfix, its likely on the big side of a code fix for what is a minor issue, but but not certain about that so will reopen to reconsider.
Updated•4 months ago
|
Description
•