1635131 - Audit existing fission-compatible actors to see if we should add messagemanagergroup restrictions to them

Status: RESOLVED WORKSFORME

(Firefox :: General, task, P3)

Description

[:Gijs (out for now; he/him)]

Support for these was added in bug 1557118. From a casual look for gBrowser mentions in browser/actors/, it would seem that a bunch of these are relying on the browser in which the child content runs being a tabbed browser. I expect a lot of them could get away with not running on other frames. This could save us some memory / CPU.

On the other hand, we'd need to be careful not to accidentally break functionality in e.g. webextension frames that we'd expect to continue working.

Comment 1

[Chris Peterson [:cpeterson]]

This bug doesn't need to block Fission MVP.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 3

[:Gijs (out for now; he/him)]

Looking at these again I'm more convinced that any uses of gBrowser are bugs and things like webrtc indicators, meta tag handling, form validation, the date/time picker and in-content prompts (alert` etc.) probably should work everywhere including for webextensions, and where they don't that just needs fixing - but we don't need to use this bug for that.