[webkit-dev] Runtime setting for incomplete features
atwilson at google.com
Mon Sep 21 11:42:54 PDT 2009
I think shooting for perfect compatibility might be nice, but is probably
I do think that we ought to be returning undefined instead of null in those
cases, though, just to catch people who are accidentally using isUndefined()
utility functions from common libraries. It would not be hard to define some
kind of [mapNullToUndefined] custom attribute for the code generator.
I'll probably be adding a flag for Chromium shared workers in the near
future, and I could tackle this at that time if people think this is a
Jeremy, do you do anything to turn off the Storage constructor (i.e.
window['Storage']) if storage is disabled?
On Fri, Sep 18, 2009 at 1:30 PM, Jeremy Orlow <jorlow at chromium.org> wrote:
> On Fri, Sep 18, 2009 at 12:59 PM, Alexey Proskuryakov <ap at webkit.org>wrote:
>> 18.09.2009, в 12:24, Jeremy Orlow написал(а):
>> I'm not sure if we've hit any compatibility issues with this yet, but it
>>> seems quite plausible that someone would compare window.localStorage (or
>>> sessionStorage or database) to undefined and, since it's null (vs.
>>> undefined), their script would assume it's available.
>> Note that they can also do '"localStorage" in window', which we can't
>> easily prevent from returning true.
> That's true. And unfortunate.
> What would be involved in making it not return true?
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev