Bugzilla

The tentative web platform tests added with Bug 1419501 to test our framebusting intervention currently only pass in mozilla-central and not in the WPT repository on GitHub. This is because our framebusting implementation is only active if `dom.disable_open_during_load` (pop-up blocking) is enabled, and that pref generally gets disabled in automation builds. In mozilla-central, we work around this by [manually disabling `dom.disable_open_during_load` again](https://searchfox.org/firefox-main/rev/70425199e9a5fa80aa7419fa51763013a67226e1/testing/web-platform/meta/html/semantics/embedded-content/the-iframe-element/iframe_top_navigation_without_user_gesture.tentative.html.ini) for the individual tests. Setting individual prefs is not possible, though, in the [main WPT GitHub repository](https://github.com/web-platform-tests/wpt) outside mozilla-central.

To address this, we should consider allowing the framebusting prevention to be enabled by `dom.security.framebusting_intervention.enabled` independently of pop-up blocking is disabled by `dom.disable_open_during_load`. The combined permission for pop-up blocking and preventing framebusting could be kept as it is right now. This would require slight UI adjustments in the settings.

To address Bug 2003033, we should consider allowing the framebusting prevention to be enabled by `dom.security.framebusting_intervention.enabled` independently of pop-up blocking is disabled by `dom.disable_open_during_load`. The combined permission for pop-up blocking and preventing framebusting could be kept as it is right now. This would require slight UI adjustments in the settings.