I think it is probably highly unlikely that an implementation would throw an exception for a known but unsupported feature but not throw an exception for a totally wacky feature. However, if isSupported is going to be tested for all known features, then you should add a wacky feature and version to cover the more likely failure of throwing an exception for an unrecognized or "malformed" feature or version. I've been putting <!-- ISSUE --> comments in tests that I think need to have an errata to resolve (which would be the case here).Received on Thursday, 25 October 2001 13:56:48 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 12:58:45 GMT