Closed
Bug 2003298
Opened 4 months ago
Closed 2 months ago
Stop using nsISearchEngine in search service notifications
Categories
(Firefox :: Search, task, P2)
Firefox
Search
Tracking
()
RESOLVED
FIXED
149 Branch
| Tracking | Status | |
|---|---|---|
| firefox149 | --- | fixed |
People
(Reporter: standard8, Assigned: mbeier)
References
Details
(Whiteboard: [sng])
Attachments
(1 file)
We are working towards removing the nsI* interfaces relating to the search service (bug 1643008).
As part of this, we can't continue to use the nsIObserverService as that would require data items to still at least use nsISupports. Therefore we should replace the observer service usages with EventEmitter.
Updated•4 months ago
|
| Assignee | ||
Comment 1•3 months ago
|
||
Using EventEmitter requires all consumers to import the search service JS module which would cause it to be loaded much earlier.
To prevent this, we decided to keep using the observer service but without nsISearchEngine by accessing wrappedJSObject instead.
Summary: Replace SearchService nsIObserveService notifications with EventEmitter → Stop using nsISearchEngine in search service notifications
| Assignee | ||
Comment 2•3 months ago
|
||
Updated•3 months ago
|
Attachment #9534490 -
Attachment description: WIP: Bug 2003298 - Stop using nsISearchEngine in search service notifications. r?standard8 → Bug 2003298 - Stop using nsISearchEngine in search service notifications. r?standard8
Pushed by mbanner@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/f7ba6c87e65a
https://hg.mozilla.org/integration/autoland/rev/87b1fe3f453d
Stop using nsISearchEngine in search service notifications. r=Standard8,urlbar-reviewers,toolkit-telemetry-reviewers,mstriemer
Comment 4•2 months ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
status-firefox149:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 149 Branch
Updated•2 months ago
|
QA Whiteboard: [search] [qa-triage-done-c149/b148]
You need to log in
before you can comment on or make changes to this bug.
Description
•