Summary: | box-shadow rendered differently from Firefox with negative spread | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Alex Yaroshevich <qfox> | ||||||||
Component: | CSS | Assignee: | Nobody <webkit-unassigned> | ||||||||
Status: | RESOLVED CONFIGURATION CHANGED | ||||||||||
Severity: | Minor | CC: | bfulgham, simon.fraser | ||||||||
Priority: | P2 | ||||||||||
Version: | 528+ (Nightly build) | ||||||||||
Hardware: | All | ||||||||||
OS: | All | ||||||||||
Attachments: |
|
Description
Alex Yaroshevich
2011-06-10 16:45:39 PDT
The attachment is a link to an image. Could you please attach (not link to) your test case? Created attachment 96853 [details]
box-shadow render diff between webkit and gecko
Yep. Sorry. I thought tracker will download it.
Created attachment 96854 [details]
testcase
Test-case for Webkit. I don't know how it can be tested).
Oops. It looks equals but it's because hack. Diff in spread-radius: -8px for webkit and -12px for gecko. But for positive numbers: 8px for webkit and 6px for gecko (or 12px for webkit and 8px for gecko). It's very strange. That's not only if spread is negative. I'm sure. I must recalculate spread-radius for pretty now by algo: If spread > 0 then firefox-spread = spread*3/2; Elseif spread < 0 then firefox-spread = spread*2/3; But if FF is doing render as told in spec I could say chrome-and-opera-radius ;-) and could do inversion of calculations. Box-shadow render with spread-radius == 0 is fine (almost equal). And don't if spread is not eq to zero. Afaik. I don't get what you're saying. Please just make a simple statement of what you think the bug is. Safari, Chrome, and Firefox all agree on rendering for this test case. I don't believe there is any remaining compatibility issue. |