This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12907 - 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.
Summary: The algorithm for parsing a legacy color value, steps 2 and 3, should be reve...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-08 09:05 UTC by contributor
Modified: 2011-08-14 06:14 UTC (History)
5 users (show)

See Also:


Attachments

Description contributor 2011-06-08 09:05:30 UTC
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
Comment 1 Simon Pieters 2011-06-08 10:35:30 UTC
Why? That doesn't match IE, IIRC. (Though the algorithm has had a number of changes away from what IE does, but still.)
Comment 2 Michael[tm] Smith 2011-08-04 05:13:49 UTC
mass-move component to LC1
Comment 3 Ian 'Hixie' Hickson 2011-08-14 06:14:19 UTC
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?