- From: Marcos Caceres <marcosscaceres@gmail.com>
- Date: Tue, 26 Apr 2011 09:56:02 +0200
- To: Bryan Sullivan <blsaws@gmail.com>
- Cc: public-webapps@w3.org, Robin Berjon <robin.berjon@gmail.com>
On Wed, Mar 9, 2011 at 11:11 AM, Bryan Sullivan <blsaws@gmail.com> wrote: > Hi all, > > I’m working to develop some widget URI tests. I notice there is nothing yet > linked from the pubstatus page. > I’ve attached a widget which performs one simple test: verify if the > window’s location.protocol attribute is “widget:”. This was modeled upon the > widget interface tests. It passes under Opera 11.01. > Looking into the other normative requirements, I’d like the group’s input on > what other requirements in the Widgets URI spec would be considered > high-priority for an “Acid test” level of support validation. I think making widget:// respond with http codes when resources are not found would be a big help. This would allow widget:// to be used with jQuery mobile and XMLHTTPRequest in general. -- Marcos Caceres http://datadriven.com.au
Received on Tuesday, 26 April 2011 07:56:53 UTC