[Bug 9049] New: What is the correct behavior if a <meta http-equiv="Content-Type"> conflicts with <meta charset>? from bugzilla@wiggum.w3.org on 2010-02-17 (public-html-bugzilla@w3.org from February 2010)

From: <bugzilla@wiggum.w3.org>
Date: Wed, 17 Feb 2010 10:51:11 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-9049-2486@http.www.w3.org/Bugs/Public/>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9049

           Summary: What is the correct behavior if a <meta http-
                    equiv="Content-Type"> conflicts with <meta charset>?
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#meta
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org,
                    wycats@gmail.com


Section: http://www.whatwg.org/specs/web-apps/current-work/#meta

Comment:
What is the correct behavior if a <meta http-equiv="Content-Type"> conflicts
with <meta charset>?

Posted from: 76.126.116.8 by wycats@gmail.com


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 17 February 2010 10:51:12 UTC