No strong opinion from me here. I'm not familiar with how Safari's UI
exposes some features but not others. In the GTK/WPE API, the features
are not enumerable and only a few selected features are exposed at all,
so that's not an issue for us.
I do think we have a semantic issue, though,
> On Feb 14, 2019, at 9:01 AM, Michael Catanzaro wrote:
>
> On Wed, Feb 13, 2019 at 9:16 PM, Simon Fraser wrote:
>> For these two, we now have them on by default because we think they are
>> ready to ship. They still exist as experimental features so that people can
>> turn them off for
On Wed, Feb 13, 2019 at 9:16 PM, Simon Fraser
wrote:
For these two, we now have them on by default because we think they
are ready to ship. They still exist as experimental features so that
people can turn them off for regression testing, but is the policy
now to move them back to Debug
> On Feb 13, 2019, at 11:32 AM, Michael Catanzaro wrote:
>
> Hi,
>
> Last year, we cleaned up experimental features in WebPreferences.yaml to
> ensure no experimental features were enabled by default. Since then we have
> regressed a bit when enabling cool new web features. :) Currently we
Hi,
Last year, we cleaned up experimental features in WebPreferences.yaml
to ensure no experimental features were enabled by default. Since then
we have regressed a bit when enabling cool new web features. :)
Currently we have 12 offenders, listed below. Most likely, the
category:
5 matches
Mail list logo
