Create a new protocol PContentContent to manage communications between contents like SyncMessage, AsyncMessage, RpcMessage, PBrowser creation, CPOW creations, PBlob creations, etc. Currently for nested oop we use two top level protocols PContent and PContentBridge to connect chrome<->content and content<->content respectively. Then we use nsIContentParent to implement the common bits. However, implementing in this way means if we modify the protocols we need to change the function signature of Content{Parent,Child}, ContentBridge{Parent,Child}, nsIContent{Parent,Child}. This is very error prone. The proposed new protocol structure is: PContent manages PContentContent PContentBridge manages PContentContent PContentContent managed by PContent or PContentBridge PContentContent manages PJavaScript, PBrowser, PBlob We might want to change the protocol names to be saner. Something like PContent -> PProcess PContentBridge -> PProcessBridge PContentContent -> PContent? but we don't have to worry about this in this bug.

I originally wanted to rename PContent to PProcess, but I believe Chris Jones had some argument against it. It may be a moot point now.

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.