[webkit-dev] On web-exposing features disabled at runtime

Sergio Villar Senin svillar at igalia.com
Mon Feb 10 23:52:26 PST 2014

En 10/02/14 22:38, Benjamin Poulain escribiu:
> On 2/10/14, 10:40 AM, Sergio Villar Senin wrote:
>> The question is whether this is an acceptable behavior or not, and how
>> to fix it in case we don't like it. I guess it's safe to conclude that
>> it isn't something that we want in general, as it might confuse web
>> authors (they see the how properties are available but do nothing).
>> Regarding how to fix it, I guess the idea is to do something similar to
>> what Eric did in Blink last year[2], i.e., filtering out the list of
>> properties that are runtime disabled.
>> Opinions?
> Can't we add a compile time flag instead?
> The chromium patch you linked is inelegant and it touches some hot paths.
> Another advantage of compile time flag is Andreas eventually notice when
> they become useless and remove all the unnecessary cruft ;)

Heh, then I won't make his life easier ;)

Seriously speaking, there was a feature flag that was removed in
https://bugs.webkit.org/show_bug.cgi?id=86767. Let's bring it to life.


More information about the webkit-dev mailing list