- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Wed, 23 Nov 2011 08:47:41 -0500
- To: ext Marcos Caceres <marcosscaceres@gmail.com>
- CC: public-webapps <public-webapps@w3.org>
On 11/21/11 12:08 PM, ext Marcos Caceres wrote:
> Hi,
> As part of LC, I've received quite a bit of offline feedback that because of some issue in Webkit, it's difficult for implementers to reuse the WebStorage interface in a widget context: the problem is that Widget's use of Web storage slightly modifies some of the behaviour of the storage methods (e.g., some things are read only and throw exceptions).
It would be useful if you would please quantify "quite a bit" and for
transparency reasons to please provide a Publicly available reference to
this "feedback".
> The way around this is to define a WidgetStorage interface that allows for the specific behaviour defined in the Widget spec.
>
> Consequently, I want to define this interface WidgetStorage in the spec:
>
> WidgetStorage : Storage{}
>
> And hence:
>
> readonly attribute Storage preferences;
>
> Becomes:
> readonly attribute WidgetStorage preferences;
>
> In practice, the addition of WidgetStorage doesn't actually affect any conforming runtimes (but allows a bunch of new Webkit ones to comply).
The proposed change would require the spec going back to LC. Is that
correct?
The proposed change, plus new test case(s) for the new feature, would
also result in the 4 implementations that now pass 100% of the test
suite, would no longer comply to the test suite until those
implementations are updated:
http://dev.w3.org/2006/waf/widgets-api/imp-report/
Is that correct?
-AB
Received on Wednesday, 23 November 2011 13:48:18 UTC