- From: Marcos Caceres <marcosscaceres@gmail.com>
- Date: Mon, 21 Nov 2011 23:19:16 +0100
- To: Robin Berjon <robin@berjon.com>
- Cc: public-webapps <public-webapps@w3.org>
On Monday, 21 November 2011 at 21:42, Robin Berjon wrote: > On Nov 21, 2011, at 18:08 , Marcos Caceres wrote: > > 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. > > > > I don't mind the change, but can you provide more details about why it's a problem with WebKit? I'm told that Web Storage in Webkit is locked up tight so you can't extend it. > If it was due to problems with what was done in the spec(s), we should document those to make sure we don't make the same mistakes again. > Yes. Simple rule: if you change the behaviour of an interface even slightly, sub-class it.
Received on Monday, 21 November 2011 22:20:02 UTC