Summary: | <body bgcolor="currentColor"> should apply #c0e000 | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Masataka Yakura <myakura.web> | ||||
Component: | DOM | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ap, ayg, tabatkins | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | Windows 7 | ||||||
Attachments: |
|
Description
Masataka Yakura
2010-09-14 00:40:39 PDT
Is this causing compat problems on any sites, or are you just noting that it doesn't match the spec? Tab Atkins has suggested WebKit's behavior be standardized: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-April/031181.html (In reply to comment #1) > Is this causing compat problems on any sites, or are you just noting that it doesn't match the spec? Tab Atkins has suggested WebKit's behavior be standardized: > > http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-April/031181.html The latter (I was playing with WebKit's HTML5 parser and found it). I don't really think if there's any sites with <font color=currentcolor> or such... For currentcolor: Trident behaves the same; Gecko seems to do what HTML5 suggests (converting "currentcolor" to #c0e000); Presto ignores the value. I don't have a strong opinion about which should be standard. https://bugs.webkit.org/show_bug.cgi?id=63029 is fixed and it resolves this, too. Does this need to have a regression test landed? (In reply to comment #4) > Does this need to have a regression test landed? Probably, yes. I can just fold this into the existing tests I added for #63029. Sounds good to me. Was it landed as part of bug 63029? I don't see such a subtest there. (In reply to comment #7) > Was it landed as part of bug 63029? I don't see such a subtest there. No, it was landed as part of bug 64576. |