Transition about:newtab/about:home/about:welcome to remote page actor instead of legacy RemotePageManager
Categories
(Firefox :: New Tab Page, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox112 | --- | affected |
People
(Reporter: Gijs, Unassigned)
Details
bug 1614713 moved all consumers of RemotePageManager off of RemotePageManager, and into actor classes that extend RemotePageChild or RemotePageParent.
... all except one! about:newtab/about:home/about:welcome is still holding out on the old infrastructure.
At the moment, this is part of what's requiring us to instantiate a BrowserTab actor for each and every page load. I'm addressing that part in bug 1718082, but I'm using a stopgap solution by moving the forced initialization of RPM into the privileged about content process and into the existing ASRouter actor. I haven't tried to touch all the messaging infrastructure itself.
I think it should be reasonably straightforward to:
- make the ASRouter actor pair inherit from RemotePageChild/Parent
- switch the 3 or so messages that it sends over the message port to use the "normal" RPM infrastructure for this instead
- then remove the legacy RemotePageManager code entirely.
This bug is here to do that work. :-)
|
||
Comment 1•2 years ago
|
||
I already did all this for bug 1814210, but never had time to polish the patch. I'll post it in that bug.
|
Reporter | |
Comment 2•2 years ago
|
||
(In reply to Neil Deakin from comment #1)
I already did all this for bug 1814210, but never had time to polish the patch. I'll post it in that bug.
Ah, drat, I didn't spot that bug when looking for it. Thank you! I'll dupe this over.
|
|
Reporter | |
Updated•2 years ago
|
Description
•