This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
mobileOK tests only apply to HTTP/HTTPS URIs, but development of Web pages often start with local authoring and many of the tests would still be useful during this first phase. Add a "direct input" method similar to that of the W3C Markup validation service: http://validator.w3.org ... and run as many tests as possible. Make sure that the report is clear about the fact that some tests could not be run and thus that the resulting page cannot be said to be mobileOK.
Direct input method added. Things worth noting: 1. the mobileOK Checker uses a fake "directinput" URI scheme to represent the URI of the content when that method is used. 2. hitting refresh on a report that used direct input returns an error when Javascript is on and an intermediary page was displayed, because the content is only sent once when the request is submitted and not when the report is displayed. 3. directinput URIs retrieval elements mimic the conventions of the HTTP URIs retrieval syntax in the moki so that tests do not need to be re-written. See Bug 6829 for more details.