This document:Public document·View comments·Disposition of Comments·
Nearby:Mobile Web Best Practices Working Group Other specs in this tool Mobile Web Best Practices Working Group's Issue tracker
Quick access to LC-1978 LC-1979 LC-1980 LC-1981 LC-1991 LC-1992 LC-2159
Previous: LC-1991 Next: LC-2159
* HTTP responses and linked resources: I understand the LINK_TARGET_FORMAT test as willing to return WARNs to the user on linked resources, and to never return any FAIL. However, there are several cases in the tests that should be carried by the checker for HTTP responses that return a FAIL, even when the resource is a linked resource: - "If an HTTP request does not result in a valid HTTP response [...], FAIL" - 1 case in "If the response is an HTTPS response" - 2 cases in "If the HTTP status indicates redirection" - "If the HTTP status represents failure (4xx), other than 404 or a request for authentication (e.g. 401), FAIL" I guess one may argue that LINK_TARGET_FORMAT may return a FAIL message. The last point still stands in that case: is a linked resource that returned a 406 Not Acceptable status supposed to trigger a FAIL? I think I should be allowed to include links to external resources that are not able to serve content to the mobileOK checker in a page without losing the possibility for the page to be mobileOK. I would relax the last check to state: "If the HTTP status represents failure (4xx), other than 404 or a request for authentication (e.g. 401): If the response relates to a request for a linked resource (see 2.4.7 Linked Resources), continue with the test (see 3.10 LINK_TARGET_FORMAT ) and warn Otherwise (i.e. for included resources), FAIL"