> On Jan 10, 2023, at 06:39, Michael Catanzaro wrote:
>
> Different default values for different ports is unavoidable; there are many
> many other examples besides PDF.js where ports just need to be different. But
> I think it's OK for the status field to be the same on all platforms. Just
>
Hi.
What status should be used for:
"Enabled by default on most platforms except those we’ve decided not to support
or if a local system dependency can’t be met but feature is still ready for
general use, but UI to toggle the feature remains to support debugging, A/B
testing."
That
On Mon, Jan 9 2023 at 02:11:37 PM -0800, Elliott Williams via
webkit-dev wrote:
- allow each port to decide whether a feature is on or off by default
(regardless of its status)
Different default values for different ports is unavoidable; there are
many many other examples besides PDF.js
Hi webkit-dev,
Brent (CC’d) and I are rolling out changes to how we represent feature flags in
WebKit. As of https://commits.webkit.org/258448@main, the WebPreferences*.yaml
files have been merged to one feature list:
Source/WTF/Preferences/UnifiedWebPreferences.yaml
Instead of having
4 matches
Mail list logo
