13849 2011-08-21 01:18:44 +0000 Refresh: HTTP header field should be defined for completeness 2011-12-02 17:40:50 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#table-http-equiv P3 normal --- 1 contributor contributor annevk ian julian.reschke mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 55540 0 contributor 2011-08-21 01:18:44 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html Multipage: http://www.whatwg.org/C#table-http-equiv Complete: http://www.whatwg.org/c#table-http-equiv Comment: Refresh: HTTP header field should be defined for completeness Posted from: 113.197.157.202 User agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.107 Safari/535.1 57823 1 ian 2011-10-04 23:45:21 +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? 57836 2 julian.reschke 2011-10-05 07:08:18 +0000 I think the request is totally clear (should I explain). (That doesn't necessarily mean I agree that it should be done over here) 57839 3 annevk 2011-10-05 07:44:48 +0000 Besides the "refresh" directive most browsers also support a Refresh HTTP header. Since HTML defines the "refresh" directive it might make sense to also define the HTTP header so we only have to define parsing here. (I did not file this bug, but it does make some sense to me.) 60794 4 ian 2011-12-02 17:40:50 +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: Rejected Change Description: no spec change Rationale: Please file HTTP bugs on the HTTP spec, not the HTML spec.