12276 2011-03-09 22:13:02 +0000 In the HTTP spec, the and that's what's related to http-equiv, it's Content-Type, not content-type etc.. I think the current definition of http-equiv needs to be revised. 2011-08-04 05:33:48 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#meta P3 normal --- 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 46590 0 contributor 2011-03-09 22:13:02 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Section: http://www.whatwg.org/specs/web-apps/current-work/#meta Comment: In the HTTP spec, the and that's what's related to http-equiv, it's Content-Type, not content-type etc.. I think the current definition of http-equiv needs to be revised. Posted from: 85.183.80.39 User agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.14) Gecko/2009090900 SUSE/3.0.14-0.1 Firefox/3.0.14 48203 1 ian 2011-05-06 19:34:06 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: I don't understand. Could you elaborate? 53847 2 mike 2011-08-04 05:33:48 +0000 mass-move component to LC1