12907 2011-06-08 09:05:30 +0000 The algorithm for parsing a legacy color value, steps 2 and 3, should be reversed. Given a case where string is a tab for instance, it should be treated as an empty string. 2011-08-14 06:14:19 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#colors P3 normal --- 1 contributor ian ayg ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 49309 0 contributor 2011-06-08 09:05:30 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html Section: http://www.whatwg.org/specs/web-apps/current-work/#colors Comment: The algorithm for parsing a legacy color value, steps 2 and 3, should be reversed. Given a case where string is a tab for instance, it should be treated as an empty string. Posted from: 213.236.208.22 User agent: Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.8.131 Version/11.11 49314 1 zcorpan 2011-06-08 10:35:30 +0000 Why? That doesn't match IE, IIRC. (Though the algorithm has had a number of changes away from what IE does, but still.) 53432 2 mike 2011-08-04 05:13:49 +0000 mass-move component to LC1 54915 3 ian 2011-08-14 06:14:19 +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: Do you have test cases demonstrating the need for this change?