Proposal: Removing ENABLE(CONTENT_EXTENSIONS)
Hi WebKittens, I would like to remove ENABLE(CONTENT_EXTENSIONS) compile time flag and always enable CONTENT_EXTENSIONS. This feature has been enabled on Apple platforms for 9 years and on GTK/WPE ports for a long time. Currently, only Windows and PlayStation ports have it disabled. Even when CONTENT_EXTENSIONS is enabled at compile time, it has no runtime effect unless content extensions backend is explicitly configured through platform-specific APIs. Since Windows and PlayStation ports don't expose such APIs, enabling this flag would only affect binary size without any behavioral changes. Given that: The feature is mature and stable (9+ years in production) Most ports already have it enabled It requires explicit API usage to activate The only impact for Windows/PlayStation is binary size I believe we can simplify the codebase by removing this compile-time flag. Best regards, Basuke Suzuki
On Wed, Jul 2 2025 at 01:45:17 PM -07:00:00, Basuke Suzuki via webkit-dev <webkit-dev@lists.webkit.org> wrote:
I believe we can simplify the codebase by removing this compile-time flag.
Surely that's fine. In general, there's no need to ask permission to remove a build flag unless (a) it guards use of some external dependency, like a library, or (b) cannot be a runtime flag for some concrete reason. Everything else should use runtime flags only. Anne has removed a lot of build flags already, but there are still a few low-hanging ones remaining, like ENABLE_FULLSCREEN_API....
participants (2)
-
Basuke Suzuki
-
Michael Catanzaro