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

Re: [widgets] HTML5 dependency blocking Widget Interface Proposed Recommendation

From: Marcos Caceres <marcosscaceres@gmail.com>
Date: Thu, 19 Apr 2012 14:06:50 +0100
To: Arthur Barstow <art.barstow@nokia.com>
Cc: public-webapps <public-webapps@w3.org>, Philippe Le H├ęgaret <plh@w3.org>, Ian Jacobs <ij@w3.org>
Message-ID: <D5491AA2CD894005B232FBF372BD1A3F@gmail.com>



On Thursday, 19 April 2012 at 13:48, Arthur Barstow wrote:

> Marcos - would you please enumerate the CR's uses of HTML5 and state 
> whether each usage is to a stable part of HTML5?


1. "A browsing context that comes into existence after initialization. The concept of a browsing context is defined in [HTML]. Multiple widget instances can be instantiated from a single widget package. A widget instance is unique and does not share any DOM attribute values, widget storage area, or [Web Storage] storage areas with any other widget instance." 

Browsing context is a concept - and a well understood one at that. 

2. "User agent implementing [HTML]'s Window interface must implement the Widget interface as the widget attribute of the window object in the manner defined by the WindowWidget interface."

The window object is present in all browser implementations. Widgets to put any additional requirements on it.  

3. "When getting or setting the preferences attribute, if the origin of a widget instance is mutable (e.g., if the user agent allows document.domain to be dynamically changed), then the user agent must perform the preference-origin security check. The concept of origin is defined in [HTML]."   

Origin is concept that is well understood - as is the same origin policy used by browsers. 

Hope that helps! 

-- 
Marcos Caceres
http://datadriven.com.au
Received on Thursday, 19 April 2012 13:07:27 GMT

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