Proposal: Remove mixed content handling settings
Hi everyone, In order to fully align with the latest Mixed Content Handling spec, bolster security, and create a better architecture for our upcoming site isolation changes, I am proposing the removal of the following settings/functions/signal below. allowRunningOrDisplayingInsecureContent isStrictMixedContentMode allowRunningOfInsecureContent allowDisplayOfInsecureContent setFoundMixedContext didDisplayInsecureContent didRunInsecureContent WebKitWebView::insecure-content-detected signal A few years ago, there was strong support for these removals here: https://github.com/WebKit/WebKit/pull/9577#discussion_r1095915718 but due to time constraints, they never happened. I’d like to restart the conversation and hopefully get these changes done. Please let me know what you think. Thanks, Ruthvik
On Tue, 2025-07-22 at 13:20 -0700, Ruthvik Konda via webkit-dev wrote:
WebKitWebView::insecure-content-detected signal
This one is public API, so it cannot be removed. It's deprecated and is no longer ever emitted unless you toggle the other settings that you're planning to remove via developer settings APIs. So you can safely delete the code that emits this signal. Michael
participants (2)
-
Michael Catanzaro
-
Ruthvik Konda