Use a unique resource listener from netmonitor in order to guarantee resource ordering
Categories
(DevTools :: Netmonitor, enhancement, P2)
Tracking
(Fission Milestone:M7, firefox83 fixed)
| Tracking | Status | |
|---|---|---|
| firefox83 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
Details
(Whiteboard: dt-fission-m2-mvp)
Attachments
(1 file, 1 obsolete file)
Bug 1663614 is going to change slightly the implementation of ResourceWatcher and from now on, the resource order is only going to be guaranteed for a given Resource Listener.
i.e. two distinct calls to ResourceWatcher.watchResources will have their onAvailable/onUpdated method called in parallel with resource arrays, which will not guarantee the resource ordering as they may received mixed resource arrays depending on their watched resources.
At least the netmonitor is surfacing such issue where two dinstict calls to watchResources are being made while resource order is very important.
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Comment 1•5 years ago
|
||
Comment 2•5 years ago
|
||
Tracking dt-fission-m2-reserve bugs for Fission Beta milestone (M7).
Updated•5 years ago
|
Comment 4•5 years ago
|
||
| bugherder | ||
Updated•5 years ago
|
Comment 5•5 years ago
|
||
Comment 7•5 years ago
|
||
Backed out for build bustages.
Log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=316382108&repo=autoland&lineNumber=8065
Backout: https://hg.mozilla.org/integration/autoland/rev/429360ccbfdb78cf1a46e6b03f716727b1899316
| Assignee | ||
Comment 8•5 years ago
|
||
Randell, you probably attached this patch to the wrong bug?
Comment 9•5 years ago
|
||
Comment on attachment 9177119 [details]
Bug 1665709: don't update session history for about:blank transient pages r=smaug
wrong bug...
Description
•