9987 2010-06-23 06:37:58 +0000 Attribute values should be allowed to contain ambiguous ampersands since large amounts of content on the web uses them in URLs and most or all web browsers already interpret them consistently. 2010-10-04 14:55:28 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#attributes-0 P3 normal --- 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 36362 0 contributor 2010-06-23 06:37:58 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#attributes-0 Comment: Attribute values should be allowed to contain ambiguous ampersands since large amounts of content on the web uses them in URLs and most or all web browsers already interpret them consistently. Posted from: 69.181.0.130 38068 1 ian 2010-08-28 00:12:38 +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: The definition of ambiguous ampersand was changed to make this less of an issue a while back.