- From: Sean Owen <srowen@google.com>
- Date: Wed, 30 Jan 2008 12:03:17 -0500
- To: "Jo Rabin" <jrabin@mtld.mobi>
- Cc: public-mobileok-checker@w3.org
Exceptions should never pop out of the library, as a rule. Francois gives examples that are just bugs, error conditions not being handled correctly. That said, if the result of a test is "not applicable", then an exception from the library is appropriate. We have not defined anything like a result type of "not applicable"; if a test simply can't be run, when runTests() is called, then this is exactly what the exception mechanism is for. I think the spec is OK, and that current behavior should be modified to not throw an exception except when the main document cannot be retrieved. On Jan 30, 2008 11:00 AM, Jo Rabin <jrabin@mtld.mobi> wrote: > > Abel makes a good point, I think. (2.2) "mobileOK tests are only meaningful when the URI under test resolves to HTML content delivered over HTTP." > > So if the test doesn't even start then that's not a FAIL. > > I'm not sure that throwing an exception is the right thing to do in this case, I would expect to see a result document stating that mobileOK was not applicable or something like that? > > I'm thinking that this situation could do with clarification in the spec. > > Jo
Received on Wednesday, 30 January 2008 17:03:32 UTC