[Bug 9847] New: I think the rules for parsing a legacy color value should specify that whitespace at the edges of the string is removed before running the rest of the algorithm. Gecko and (if my memory is correct) WebKit both do this, so it's certainly Web-compatible be

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9847

           Summary: I think the rules for parsing a legacy color value
                    should specify that whitespace at the edges of the
                    string is removed before running the rest of the
                    algorithm.  Gecko and (if my memory is correct) WebKit
                    both do this, so it's certainly Web-compatible be
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#col
                    ors
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org


Section: http://www.whatwg.org/specs/web-apps/current-work/#colors

Comment:
I think the rules for parsing a legacy color value should specify that
whitespace at the edges of the string is removed before running the rest of
the algorithm.    Gecko and (if my memory is correct) WebKit both do this, so
it's certainly Web-compatible behavior.  And it seems quite odd for <body
bgcolor=" red"> to fall through to the legacy color parsing algorithm rather
than producing the obvious result.

Posted from: 63.245.220.240

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 3 June 2010 23:09:40 UTC