W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2013

Re: Forbid constants on [noInterfaceObject] interfaces

From: David Bruant <bruant.d@gmail.com>
Date: Wed, 31 Jul 2013 18:43:09 +0200
Message-ID: <CAHbscB2OzhQ-NxOxi+PxvBnd=dYDbJ_To7No3Uk5gwTMsdyxUA@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: "public-script-coord@w3.org" <public-script-coord@w3.org>
2013/7/31 Boris Zbarsky <bzbarsky@mit.edu>

> On 7/31/13 5:21 AM, David Bruant wrote:
>
>> This results in TEMPORARY and PERSISTENT global properties. Look in a
>> recent Chrome console.
>>
>
> That sounds like a bug in Chrome, pure and simple.

given how they promote the feature [1] (see code snippets in the article,
it has both "PERSISTENT" and window.TEMPORARY), I doubt this is a bug.
Worse, I doubt this can be changed.


>
>  I'll take the time later to send feedback to the File API people to see
>> if this can be changed.
>>
>
> In this case, I suspect that the LocalFileSystem interface should in fact
> have an interface object...

Agreed. i'll start a thread on public-webapps.

David

[1] http://www.html5rocks.com/en/tutorials/file/filesystem/
Received on Wednesday, 31 July 2013 16:43:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:50 UTC