[meta] Make partial CDP implementation Fission compatible
Categories
(Remote Protocol :: CDP, task)
Tracking
(Not tracked)
People
(Reporter: whimboo, Unassigned)
References
(Depends on 3 open bugs, Blocks 1 open bug)
Details
(Keywords: meta)
This bug will track the work that needs to be done to make the Remote Agent Fission compatible.
Comment 1•5 years ago
|
||
Tracking for Fission Nightly (M6)
Updated•4 years ago
|
Comment 3•4 years ago
|
||
Moving Remote Protocol bugs to Fission Beta milestone (M7).
Reporter | ||
Updated•4 years ago
|
Comment 4•4 years ago
|
||
DevTools meta bugs don't need to block Fission MVP. However, we will continue to monitor these meta bugs for any new bugs blocking them as potential blockers for Fission MVP.
Reporter | ||
Comment 5•3 years ago
|
||
Nowadays it's not the Remote Agent that isn't Fission compatible but the CDP implementation. Maybe we can re-use the message handler architecture as implemented for WebDriver BiDi to also make CDP Fission compatible.
Reporter | ||
Comment 6•3 years ago
|
||
Now with bug 1601245 fixed we have basic Fission support, which includes that BFCacheInParent is disabled and all web pages are forced to a single shared content process. For now we are not planning further work, unless one of the prefs to control both states is going to be removed.
Reporter | ||
Updated•3 years ago
|
Updated•2 years ago
|
Reporter | ||
Comment 7•2 years ago
|
||
The changes in bug 1819965 helped a bit here given that we will no longer hang for certain commands if the underlying browsing context / message manager gets replaced. Nevertheless we still have a lot of state that we hold on the child process and that is not going to work well with Fission. As such our implementation still suffers proper support and we requested the Selenium project to deprecate its usage in favor of WebDriver BiDi.
Description
•