- From: Marcos Caceres <marcosc@opera.com>
- Date: Fri, 5 Feb 2010 16:18:34 +0100
- To: cyril.concolato@telecom-paristech.fr
- Cc: public-webapps <public-webapps@w3.org>
On Thu, Feb 4, 2010 at 6:41 PM, Cyril Concolato <cyril.concolato@enst.fr> wrote: > Hi all, > > After P&C, I'm looking now at the Widget Interface spec, in particular to > check the test suite and produce the implementation report. I have a problem > with the spec. In GPAC, we implement only SVG not HTML5, with the Window > object. Hmm... to support SVG, what we should do is externalize the javascript of each test. Then just use a script element to include the same code into both files. Do you think you could help me do this? Basically, what we would need to do is: 1. check if the current scripts work in an SVG context - and fix if they don't. 2. make the SVG templates (index.svg). 3. externalize all the JS (call them all test.js). 4. Replace all the HTML files. I'm not sure what we will do with all the automatically generated tests. We will need some guidance there from Dom, as I don't know how that generator works. >So I'm wondering how should the widget object be implemented in a UA > that does not support the window object ? Yeah, that's a tough one... the spec says: "For a widget instance, a user agent MUST expose a unique object that implements the widget interface to author scripts." It does not give any guidance as to how the interface must be exposed. -- Marcos Caceres http://datadriven.com.au
Received on Friday, 5 February 2010 15:19:28 UTC