W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: RfC: moving Web Storage to WG Note; deadline June 29

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Tue, 21 Jun 2011 09:50:18 -0400
Message-ID: <4E00A19A.8060700@mit.edu>
To: Marcos Caceres <marcosscaceres@gmail.com>
CC: Jonas Sicking <jonas@sicking.cc>, Anne van Kesteren <annevk@opera.com>, public-webapps <public-webapps@w3.org>, Arthur Barstow <art.barstow@nokia.com>
On 6/21/11 2:00 AM, Marcos Caceres wrote:
>>> Browser extensions are in every browser, so in a sense are part of the
>>> web platform.
>>
>> I strongly object to both this claim and the idea that browser extension
>> concerns should affect web-exposed APIs in general....
>
> your claims seem pretty groundless given the fact the Storage is
> implemented and used in exactly the same way on the web, in
> extensions, and in widgets. I really don't know what you possibly
> could be objecting to?

I'm objecting to the claim that browser extensions are part of the web 
platform and hence should inform the design of web APIs.  They are not 
and they should not, except in cases where there are no web 
considerations informing the API.

> If that is so, then prove it: how *localStorage* in Opera extensions
> and Chrome extensions as used by background pages in any way different
> from localStorage on a Web page? What are these "all sorts of ways"
> that I so naively fail to miss?

Typically, the security restrictions applied to browser extensions are 
completely different from the ones applied to websites, as one simple 
example....

-Boris
Received on Tuesday, 21 June 2011 13:50:49 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:45 GMT