Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 194d557d4fa67bcc2a3e9c929d142b8035067209
https://github.com/WebKit/WebKit/commit/194d557d4fa67bcc2a3e9c929d142b8035067209
Author: Anne van Kesteren <[email protected]>
Date: 2026-09-07 (Mon, 07 Sep 2026)
Changed paths:
M Source/WTF/Scripts/GeneratePreferences.rb
M Source/WTF/Scripts/Preferences/UnifiedWebPreferences.yaml
M Source/WebCore/Scripts/GenerateSettings.rb
M Source/WebCore/Scripts/SettingsTemplates/Settings.cpp.erb
Log Message:
-----------
Retire webcoreBinding and exposed from UnifiedWebPreferences.yaml
https://bugs.webkit.org/show_bug.cgi?id=323609
Reviewed by Chris Dumez.
93 "webcoreBinding: none" and 2 "webcoreBinding: custom" entries were
redundant. Being excluded from WebCore already says there is no binding. The
14 that remain say "webcoreDeprecatedGlobalSettings: true", the only choice
the key ever made that generated anything.
ForceEnhancedSecurity and SWVPDecodersAlwaysEnabled had to be excluded from
WebCore first: both said "webcoreBinding: none" while claiming to be in
WebCore, so the derivation finds 673 preferences bound to Settings where
"!webcoreBinding" found 671. SWVPDecodersAlwaysEnabled's WebCore default
value, which nothing read, is also removed.
"exposed" becomes "webKitLegacyExposed: false", because WebKit1 is the only
frontend that ever read it: GeneratePreferences.rb is never run with
--frontend WebCore and GenerateSettings.rb ignores the key, and no preference
is in WebKit without being exposed there. 84 of the 85 lists said nothing but
"not part of the WebKit1 API"; the one naming only WebKitLegacy is dropped,
since exposed is the default.
No behavior change: generating every derived file for all six generator
invocations before and after produces 23 byte-identical files.
Canonical link: https://commits.webkit.org/320640@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
