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

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

From: Glenn Adams <glenn@skynav.com>
Date: Thu, 19 Apr 2012 08:58:00 -0600
Message-ID: <CACQ=j+f0SgB02-uTzr+coOvO3THVBzO=C4DpYcwQaPBAsmU62w@mail.gmail.com>
To: Marcos Caceres <marcosscaceres@gmail.com>
Cc: Arthur Barstow <art.barstow@nokia.com>, Philippe Le H├ęgaret <plh@w3.org>, Ian Jacobs <ij@w3.org>, WebApps WG <public-webapps@w3.org>
On Thu, Apr 19, 2012 at 7:06 AM, Marcos Caceres <marcosscaceres@gmail.com>wrote:

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

TWI [1] does not define "the origin of a widget instance". Nor does HTML5.
It is also confusing to say that HTML5 defines the 'concept of origin',
given that it normatively refers to The Web Origin Concept [2]. TWI needs
to be more specific about what aspect of Origin is being referenced and
where that specific aspect is defined.

[1] http://www.w3.org/TR/2011/CR-widgets-apis-20111213/
[2] http://tools.ietf.org/html/rfc6454
Received on Thursday, 19 April 2012 14:58:56 GMT

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