- From: Steve Block <steveblock@google.com>
- Date: Thu, 3 Dec 2009 15:21:41 +0000
- To: Max Froumentin <maxfro@opera.com>
- Cc: Andrei Popescu <andreip@google.com>, public-geolocation <public-geolocation@w3.org>
>>> Test 00133: call watchPosition() with wrong type for third argument. Exception expected. >> I don't think that any type passed for the positionOptions argument >> should cause an exception. The spec states that 'PositionOptions >> objects are regular ECMAScript objects ...' and all of its properties >> are optional. In JS, any type can be converted to a (perhaps empty) >> object. The implementation should simply check for the presence of the >> relevant properties, but never throw an exception. See the WebKit test >> linked above. > > Do you think that the specification should be more explicit about the above? That's probably a good idea. >>> Test 00031: pass if getCurrentPosition returns withing 100ms >> >> I'm not sure it's useful to test that the function returns within a >> particular time limit, as the spec doesn't specify such a limit. I >> think the important thing to check is that the callbacks are always >> invoked asynchronously, rather than from within the function call. > > The statement that this test is checking is "must immediately return", > though. Clearly the test isn't great but I can't think of another way to > check. Sure, but I think the intent of the spec is not to limit the time taken by the method to return, but to require that the location acquisition process and the callbacks should be asynchronous. Andrei, can you clarify? Steve -- Google UK Limited Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W 9TQ Registered in England Number: 3977902
Received on Thursday, 3 December 2009 15:22:22 UTC