Use DOCUMENT_EVENT's will-navigate event to clear ResourceCommand internal cache
Categories
(DevTools :: Framework, task)
Tracking
(Fission Milestone:M8, firefox91 fixed)
Tracking | Status | |
---|---|---|
firefox91 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
(Blocks 1 open bug)
Details
(Whiteboard: dt-fission-m3-mvp)
Attachments
(3 files)
Bug 1712592 introduced DOCUMENT_EVENT will-navigate resource in order to replace target's will-navigate event.
ResourceCommand is still using the target event and should use the resource instead, which is more resilient with cross process navigation.
Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 2•3 years ago
|
||
We were calling ResourceCommand.watchResources from onTargetAvailable, whereas we could and should
call it once before or after calling TargetCommand.watchTargets.
Doing this helps calling watchResources only once, for all the resource types.
Also tweaked networkFront and responsiveFront instantiation.
to only instantiate them when we need them.
Assignee | ||
Comment 3•3 years ago
|
||
Doing this helps knowing if some resources are coming from ResourceCommand cache,
or if they are live resources coming from the server.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 5•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/ffb738eeaa47
https://hg.mozilla.org/mozilla-central/rev/820149ffdf51
https://hg.mozilla.org/mozilla-central/rev/77d3ebb0c056
Description
•