[Widgets] CfC: add WidgetStorage interface to API spec; deadline December 1

Below, Marcos proposed a change request to the Widget Interface spec and 
this is a Call for Consensus to accept this proposal and to update the 
spec accordingly.

Marcos asserted in followups to his proposal that this change would not 
affect any implementations nor applications. As such, the change 
request, if applied, will not require republication as a new (LC)WD.

Note this spec is currently in the LCWD phase and given there are 
already more than two implementations that pass 100% of the test suite, 
the only reason this spec is not already a Recommendation is because it 
is blocked by the W3C's dependency maturity rules (Web IDL, Web Storage 
in particular).

Positive response to this CfC is preferred and encouraged and silence 
will be considered as agreeing with Marcos' proposal. The deadline for 
comments is December 1 and all comments should be sent to public-webapps 
at w3.org.

-AB

-------- Original Message --------
Subject: 	[Widgets] WidgetStorage interface
Resent-Date: 	Mon, 21 Nov 2011 17:09:42 +0000
Resent-From: 	<public-webapps@w3.org>
Date: 	Mon, 21 Nov 2011 18:08:56 +0100
From: 	ext Marcos Caceres <marcosscaceres@gmail.com>
To: 	public-webapps <public-webapps@w3.org>



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). 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).

Kind regards,
Marcos

-- 
Marcos Caceres
http://datadriven.com.au

Received on Thursday, 24 November 2011 14:37:03 UTC