Closed
Bug 1833990
Opened 2 years ago
Closed 2 years ago
Use ChromeUtils.idleDispatch instead of nsIMessageLoop.postIdleTask
Categories
(GeckoView :: General, task, P3)
Tracking
(firefox115 fixed)
RESOLVED
FIXED
115 Branch
Tracking | Status | |
---|---|---|
firefox115 | --- | fixed |
People
(Reporter: m_kato, Assigned: m_kato)
References
Details
Attachments
(1 file)
GeckoView's DelayedInit.jsm
is only one consumer for nsIMessageLoop
. Actually, ChromeUtils
has idleDispatch
, or Timer.sys.mjs
has requestIdleCallback
. So we can replace nsIMessageLoop
with ChromeUtils.idleDispatch
.
Assignee | ||
Comment 1•2 years ago
|
||
GeckoView's DelayedInit.jsm
is only one consumer for nsIMessageLoop
. This
XPCOM has no unit test now, so we don't know whether this XPCOM works
correctly.
Actually, ChromeUtils
has idleDispatch
, so we can replace nsIMessageLoop
with ChromeUtils.idleDispatch
. It is used on a lot of code.
Pushed by m_kato@ga2.so-net.ne.jp:
https://hg.mozilla.org/integration/autoland/rev/ddf9ed515362
Use ChromeUtils.idleDispatch instead of nsIMessageLoop.postIdleTask. r=geckoview-reviewers,calu
Comment 3•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox115:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•