Custom Query (133 matches)
Results (1 - 3 of 133)
|#133||invalid||Remove invalid warnings for encoding and mime when declaring support in headers.||--||John A. Bilicki III|
The mobileOK Checker warns about XHTML 1.1 doctype and the UTF-8 encoding however with the latest builds of my site that I have been validating against I do not serve the doctype or encoding or doctype unless support is explicitly declared in the http_accept or http_charset headers.
These warnings would only be valid if these headers did not explicitly declare support for the doctype or encoding.
Therefore these warnings should be removed.
|#235||duplicate||Bad link to i18n checker||--||Richard Ishida|
The icon after "Results for the test: W3C Internationalization Checker" produces a page that complains about XML errors, rather than taking you to the i18n checker.
|#252||invalid||False, compounding errors on seemingly-compliant document.||--||aaron@…|
A conformance check on http://magnifi.ca/photos/concept/everydotcom/ is showing several plainly false errors, which are spiralling off to trigger even more.