ISSUE-21: should Widgets 1.0 allow fallback for <content> element?
should Widgets 1.0 allow fallback for <content> element?
- State:
- CLOSED
- Product:
- HISTORICAL: Widgets [Bugs and Issues are tracked via Bugzilla https://www.w3.org/Bugs/Public/describecomponents.cgi?product=WebAppsWG]
- 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:
- Re: ISSUE-21: should Widgets 1.0 allow fallback for <content> element? [Widgets] (from art.barstow@nokia.com on 2008-08-30)
- ISSUE-21: should Widgets 1.0 allow fallback for <content> element? [Widgets] (from sysbot+tracker@w3.org on 2008-06-27)
Related notes:
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>
Display change log
