17583 2012-06-24 11:22:06 +0000 misleading statements about fragment identifiers in application-x-www-form-urlencoded media type 2012-11-04 11:10:47 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified All All RESOLVED FIXED http://dev.w3.org/html5/spec/single-page.html#application-x-www-form-urlencoded P2 normal --- 1 julian.reschke silviapfeiffer1 mike public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 69361 0 julian.reschke 2012-06-24 11:22:06 +0000 "Fragment identifiers have no meaning with the application/x-www-form-urlencoded type as this type is only used for uploaded payloads that do not have URL identifiers." That is misleading, because there's no reason why this media type couldn't show up in a payload of a GET response. Suggest to simply state: "This specification does not define fragment identifier semantics for this media type". 70237 1 contributor 2012-07-18 07:11:49 +0000 This bug was cloned to create bug 17883 as part of operation convergence. 77830 2 silviapfeiffer1 2012-11-04 11:10:47 +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-v2.html Status: Accepted Change Description: https://github.com/w3c/html/commit/3b1ee7b24abfc94f2bdb421802d4b1db644d544d Rationale: adopted change of WHATWG