5358 2008-01-11 18:19:01 +0000 No errors on HTTP errors 2008-04-11 07:45:00 +0000 1 1 1 Unclassified mobileOK Basic checker Java Library unspecified All Linux RESOLVED FIXED P2 normal --- 1 srowen abel.rionda oldest_to_newest 18277 0 srowen 2008-01-11 18:19:01 +0000 As far I can tell, we don't have any code in place currently to report the errors described in http://www.w3.org/TR/mobileOK-basic10-tests/#http_response and http://www.w3.org/TR/mobileOK-basic10-tests/#meta_http_equiv Can someone confirm so? If that's the case, this is definitely a todo item for moving to beta. As I noted in one of my (numerous, sorry about that) other messages, there is at least one case where an HTTP error is reported through an individual test (GRAPHICS_FOR_SPACING); I'm thinking that when we encounter an HTTP error, we probably shouldn't run the other relevant tests on the said resource at all. If so, maybe we should have something in the moki document to mark up the resources that triggered an HTTP error (as defined as a fail in #http_response), so that we can easily avoid them in the XSLT-based tests. 18415 1 dom 2008-01-18 11:31:13 +0000 Initial work checked in by Abel and Miguel. Now needs to add test cases, associated error messages and handling in XSLT. Also needs to fix other tests so that they don't get triggered when an HTTP error was encountered in the process. 19783 2 abel.rionda 2008-04-11 07:45:00 +0000 Added meta_http_equiv-2 (Test case MAIN_DOCUMENT 6) Added http_response-7 (Test cases MAIN_DOCUMENT 7 and IMAGE_SPECIFY_SIZE 7)