ISSUE-21

should Widgets 1.0 allow fallback for <content> element?

State:
CLOSED
Product:
Widgets
Raised by:
Marcos Caceres
Opened on:
2008-06-27
Description:
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>
Related Actions Items:
No related actions
Related emails:
  1. Re: ISSUE-21: should Widgets 1.0 allow fallback for <content> element? [Widgets] (from art.barstow@nokia.com on 2008-08-30)
  2. ISSUE-21: should Widgets 1.0 allow fallback for <content> element? [Widgets] (from sysbot+tracker@w3.org on 2008-06-27)

Related notes:

2008-08-30 14:20:41: This issue has been closed, based on the WG's agreement on August 27. Please see the following for details:

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

Display change log ATOM feed


Charles McCathieNevile <chaals@opera.com>, Arthur Barstow <art.barstow@nokia.com>, Chairs, Doug Schepers <schepers@w3.org>, Staff Contact
Tracker, originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.231 2009/11/16 15:00:54 dom Exp $