Closed
Bug 1895960
Opened 11 days ago
Closed 7 days ago
Only pass the queryCharset through to ParamSubstitution rather than a full engine object
Categories
(Firefox :: Search, task, P3)
Firefox
Search
Tracking
()
RESOLVED
FIXED
128 Branch
Tracking | Status | |
---|---|---|
firefox128 | --- | fixed |
People
(Reporter: standard8, Assigned: standard8)
Details
Attachments
(1 file)
In the SearchEngine
/ EngineURL
we are passing a full SearchEngine
object through getSubmission
and onto ParamSubstitution
. However, we are only using the queryCharset
from that engine.
The problem with this is that it makes it unclear what getSubmission
and ParamSubstitution
are actually doing with the engine object. I think it would be clearer and simpler to only pass the queryCharset
.
Assignee | ||
Comment 1•11 days ago
|
||
This helps with clarity to know exactly what getSubmission/ParamSubstitution require, rather than passing a general engine object, which could be anything.
Pushed by mbanner@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5cb9241bfb7e Only pass the queryCharset through to ParamSubstitution rather than a full engine object. r=search-reviewers,daleharvey
Comment 3•7 days ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 7 days ago
status-firefox128:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•