W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2008

Re: ISSUE-21: should Widgets 1.0 allow fallback for <content> element? [Widgets]

From: Arthur Barstow <art.barstow@nokia.com>
Date: Sat, 30 Aug 2008 10:21:12 -0400
Message-Id: <B38223F9-E43C-4506-B57F-BB0AD6E4511E@nokia.com>
To: Web Applications Working Group WG <public-webapps@w3.org>

This issue has been closed, based on the WG's agreement on August 26.  
Please see the following for details:

  <http://www.w3.org/2008/08/26-wam-minutes.html#item14>

-Regards, Art Barstow


On Jun 27, 2008, at 12:30 AM, ext Web Applications Working Group  
Issue Tracker wrote:

>
> ISSUE-21: should Widgets 1.0 allow fallback for <content> element?  
> [Widgets]
>
> http://www.w3.org/2008/webapps/track/issues/
>
> Raised by: Marcos Caceres
> On product: Widgets
>
> Currently, only one <content> element is allowed in a configuration  
> document. This means that authors can't point to alternative  
> representations of their widgets. For example, I might want to load  
> a flash version, and, failing that I might want to load a HTML  
> version. this could maybe be solved by allowing something similar to:
>
> <content src="someFile" type="some/mediaType">
>   <content src="someOtherFile"type="text/html"/>
> </content>
>
>
>
>
>
Received on Saturday, 30 August 2008 14:22:00 GMT

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