13713 2011-08-09 13:52:03 +0000 Remove step 7 "Replace any characters in input that have a Unicode code point greater than U+FFFF (i.e. any characters that are not in the basic multilingual plane) with the two-character string "00"." if the algorithm is dealing with UTF-16 code units (" 2011-10-06 23:49:49 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#rules-for-parsing-a-legacy-color-value P3 normal --- 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking zcorpan public-html-bugzilla oldest_to_newest 54455 0 contributor 2011-08-09 13:52:03 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/common-microsyntaxes.html Multipage: http://www.whatwg.org/C#rules-for-parsing-a-legacy-color-value Complete: http://www.whatwg.org/c#rules-for-parsing-a-legacy-color-value Comment: Remove step 7 "Replace any characters in input that have a Unicode code point greater than U+FFFF (i.e. any characters that are not in the basic multilingual plane) with the two-character string "00"." if the algorithm is dealing with UTF-16 code units ("Yeah this is fallout from the decision to stop having the spec be in terms of Unicode but instead have the spec in terms of UTF-16 code points." -- http://www.w3.org/Bugs/Public/show_bug.cgi?id=13676 ) Posted from: 88.131.66.80 by simonp@opera.com User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.5.8; U; en) Presto/2.9.168 Version/11.50 57925 1 ian 2011-10-06 23:49:49 +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: With the new definitions, this now all just works as specced.