Re: Status of Selectors API Level 1 Candidate

2011-02-22 Thread Arve Bersvendsen
On Tue, 22 Feb 2011 22:40:34 +0100, Mike Taylor wrote: http://dev.w3.org/2006/webapi/selectors-api-testsuite/003.html I get a 404. http://dev.w3.org/2006/webapi/selectors-api-testsuite/003.xhtml -- Arve Bersvendsen Opera Software ASA, http://www.opera.com/

Re: Status of Selectors API Level 1 Candidate

2011-02-22 Thread Arthur Barstow
On Feb/22/2011 4:40 PM, ext Mike Taylor wrote: http://dev.w3.org/2006/webapi/selectors-api-testsuite/003.html I get a 404. The above is missing and "x" and should be: http://dev.w3.org/2006/webapi/selectors-api-testsuite/003.xhtml

Re: Status of Selectors API Level 1 Candidate

2011-02-22 Thread Mike Taylor
(Using IE9 RC1) On 2/22/11 4:17 PM, Charles McCathieNevile wrote: http://dev.w3.org/2006/webapi/selectors-api-testsuite/001.html 100% http://dev.w3.org/2006/webapi/selectors-api-testsuite/002.html 100% http://dev.w3.org/2006/webapi/selectors-api-testsuite/003.html I get a 404. Cheers,

Re: Status of Selectors API Level 1 Candidate

2011-02-22 Thread Charles McCathieNevile
Hi folks, I am putting together an implementation report for Selectors API, but I don't have handy access to a copy of Windows/IE9 - if anyone who does has the couple of minutes needed to visit http://dev.w3.org/2006/webapi/selectors-api-testsuite/001.html http://dev.w3.org/2006/webapi/selec

Re: Status of Selectors API Level 1 Candidate

2010-05-06 Thread Boris Zbarsky
On 5/6/10 10:44 AM, Stewart Brodie wrote: Taking the null, explicit undefined and implicit undefined test cases together, I don't think I've got any two browsers here that behave the same way. :-/ Yes, that's why we can't exit CR. ;) Note that part of the issue here is that the spec flip-flop

Re: Status of Selectors API Level 1 Candidate

2010-05-06 Thread Stewart Brodie
Lachlan Hunt wrote: > I believe the test suite is nearly ready [1]. > > As I mentioned last year, Minefield currently passes 100% of the test > suite. However, this has not yet shipped in a release build. I assume it > will make it into the next major release after the current 3.6.x branch. >

Re: Status of Selectors API Level 1 Candidate

2010-05-05 Thread Thomas Broyer
On Wed, May 5, 2010 at 4:28 PM, Tab Atkins Jr. wrote: > On Wed, May 5, 2010 at 4:56 AM, Lachlan Hunt wrote: >> I have not been able to test IE9 because I don't have access to Windows >> Vista or 7.  I would appreciate it if anyone who has a copy of the last >> public development build, or someone

Re: Status of Selectors API Level 1 Candidate

2010-05-05 Thread Tab Atkins Jr.
On Wed, May 5, 2010 at 4:56 AM, Lachlan Hunt wrote: > I have not been able to test IE9 because I don't have access to Windows > Vista or 7.  I would appreciate it if anyone who has a copy of the last > public development build, or someone from Microsoft, could report on the > implementation status

Re: Status of Selectors API Level 1 Candidate

2010-05-05 Thread Lachlan Hunt
+public-webapps, -team-webapps On 2010-05-04 18:23, Arthur Barstow wrote: The Selectors API Candidate says: [[ http://www.w3.org/TR/2009/CR-selectors-api-20091222/ There are several known implementations believed to be complete and interoperable (or on the point of being so) and the WebApps Wo