W3C home > Mailing lists > Public > www-validator-cvs@w3.org > January 2013

[Bug 20765] New: Nuts warning for "lax content-type" when Content-Type is text/html and lacks charset parameter

From: <bugzilla@jessica.w3.org>
Date: Fri, 25 Jan 2013 00:03:09 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-20765-169@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20765

            Bug ID: 20765
           Summary: Nuts warning for "lax content-type" when Content-Type
                    is text/html and lacks charset parameter
    Classification: Unclassified
           Product: Validator (Nu)
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: General
          Assignee: mike+validator@w3.org
          Reporter: xn--mlform-iua@xn--mlform-iua.no
        QA Contact: www-validator-cvs@w3.org

Created attachment 1317
  --> https://www.w3.org/Bugs/Public/attachment.cgi?id=1317&action=edit
Screenshot of meaningless warning.

Steps to repeat:

1. Locate a page of the following characteristics:
   a. has XHTML5 markup.
   b. has <meta charset="UTF-8"/>
   c. has Content-Type text/html *without* charset parameter
   d. is served via HTTP or via data URI
2. Check the page with XML parser: http://tinyurl.com/a95tvf8

Expected result: Since the page contains <meta charset="UTF-8"/>
                 the page uses UTF-8 encoding in the text/html 
                 Content-Type and will therefore not cause any 
                 error message despite that the Content-Type
                 lacks the charset parameter: 
                 http://tinyurl.com/aeuwqz9

                 Therefore I wouldn't expect that overriding the
                 Content-Type ("lax about Content-Type") would 
                 cause any warning with regard to the charset
                 paramter of the *original* Content-Type.

  Actual result: Validator gives a confusing message were it
                 claims that it, quote, "Would have defaulted to 
                 US-ASCII had the lax option not been chosen."

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 25 January 2013 00:03:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 25 January 2013 00:03:12 GMT