Some ResponsiveActor methods do a bit more than setting the flag on the browsing context, so we might still keep them, and make the RDM ui use targetConfigurationCommand that will abstract calls to both parent and content processes.

Tracking this dt-fission-m3-mvp bug for Fission M8 milestone since this blocks meta bug 1690100 ("Set BrowsingContext flags from the parent process"), which is being tracked for Fission M8.

This bug is assigned to Fission Milestone M8, but has whiteboard tag dt-fission instead of dt-fission-m3-mvp.

I'm adding the dt-fission-m3-triage tag so DevTools Fission triage can decide whether this bug should be fixed for dt-fission-m3-mvp or can be postponed from Fission Milestone MVP to Future.

Removing triage whiteboard tag as meta bugs are not included as part of the project's MVP backlog. If there are individual dependencies which should be considered the whiteboard tag can be added to them.

(In reply to Marco Mucci [:MarcoM] from comment #3)

Removing triage whiteboard tag as meta bugs are not included as part of the project's MVP backlog. If there are individual dependencies which should be considered the whiteboard tag can be added to them.

Thanks. In that case, I will move this meta bug from Fission Milestone M8 to Future.

This meta bug has one blocking bug that is still open (bug 1706091) and it is not tracked for dt-fission-m3-mvp.