[webkit-dev] Runtime setting for incomplete features

Drew Wilson atwilson at google.com
Wed Sep 23 18:17:15 PDT 2009

Yeah, I'm thinking A also. OK, sounds like we're on the same page for A
(which is all I really care about). For B it does impact the web app's
ability to do capabilities detection which seems bad, but it's not worth
arguing about hypotheticals I think.

On Wed, Sep 23, 2009 at 6:10 PM, Maciej Stachowiak <mjs at apple.com> wrote:

> On Sep 23, 2009, at 6:05 PM, Peter Kasting wrote:
> On Wed, Sep 23, 2009 at 6:03 PM, Maciej Stachowiak <mjs at apple.com> wrote:
>> My thinking on the topic is basically this:
>> A) For experimental features, it makes sense to make them disappear
>> completely when turned off, since turning them on is an unusual and
>> experimental state.
>> B) For end-user features that are on by default but have a preference to
>> turn them off, having APIs appear and disappear fragments the platform.
> I believe most of the cases where this occurs in Chromium are instances of
> A.  We don't tend to expose prefs to do B.
> That is what I would expect. My earlier email exchange with Jeremy got into
> this side track, but it doesn't seem like something that would be common.
> Regards,
> Maciej
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20090923/5711dde4/attachment.html>

More information about the webkit-dev mailing list