6966 2009-05-27 11:50:31 +0000 LINK_TARGET_FORMAT-1: javascript URIs should not be reported 2009-05-29 14:24:47 +0000 1 1 1 Unclassified mobileOK Basic checker Java Library unspecified PC Linux RESOLVED FIXED P2 normal --- 1 fd fd oldest_to_newest 25330 0 fd 2009-05-27 11:50:31 +0000 The test should apply to linked resources, defined in the spec as URIs with the scheme http and https: http://www.w3.org/TR/mobileOK-basic10-tests/#linked_resources In particular, javascript URIs should not be treated as linked resources, and the warning should not be triggered by such URIs. See for instance the result of the checker on: http://cnn.com This bug was introduced in the overhauled version. The comment that describes the implementations of the ResourceExtractor interface claims: [[ URIs whose scheme is not supported are ignored. As far as mobileOK is concerned, this means that URIs must use the scheme HTTP or HTTPS, but note the code actually relies on the list of ResourceRetriever defined in TesterConfiguration. ]] The comment is right, but the code actually doesn't check anything, and extracts all kinds of URIs. These URIs then appear in the moki document in the links, images, objects sections. They should not appear there 25364 1 fd 2009-05-29 14:24:47 +0000 Extractors updated to ignore unknown schemes. The ResourceExtractorFactory interface had to be completed with a isSchemeSupported method. Ignoring an unknown scheme is what the mobileOK spec imposes but I still find it a bit strange not to raise at least a warning when e.g. an image whose URI is of an unknown scheme is encountered. I raised a similar comment a long time ago in: http://lists.w3.org/Archives/Public/public-mobileok-checker/2008Jan/0125.html