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

[widgets] Please include a statement of purpose and user interaction expectations for <feature>

From: Henri Sivonen <hsivonen@iki.fi>
Date: Tue, 2 Jun 2009 15:57:46 +0300
Message-Id: <E9A57FBA-418E-49D4-A240-851D1881366D@iki.fi>
To: public-webapps <public-webapps@w3.org>
Please state the purpose of <feature>. (That it's for authorizing  
features that don't participate in the Web-oriented browser security  

Please include a corresponding UA requirement to obtain authorization  
from the user for the features imported with <feature>. (It seems that  
the security aspect requires an authorization and doesn't make sense  
if the dangerous feature are simply imported silently.) As far as I  
can tell, the spec doesn't currently explain what the UA is supposed  
to do with the 'feature list' once built.

Henri Sivonen
Received on Tuesday, 2 June 2009 12:58:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:12:53 UTC