Bug 103754

Summary: Fonts too thin in certain conditions
Product: WebKit Reporter: Michał Gołębiowski-Owczarek <m.goleb+bugzilla>
Component: TextAssignee: Nobody <webkit-unassigned>
Status: UNCONFIRMED ---    
Severity: Normal CC: simon.fraser
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Mac (Intel)   
OS: OS X 10.8   
URL: http://wystawy.bn.org.pl/ptolemeusz/corridor/
Attachments:
Description Flags
Chrome Canary screenshot (in Firefox stable it looks the same)
none
Webkit Nightly screenshot (in Chrome stable it looks the same) none

Description Michał Gołębiowski-Owczarek 2012-11-30 09:58:36 PST
Created attachment 176985 [details]
Chrome Canary screenshot (in Firefox stable it looks the same)

1) Open http://wystawy.bn.org.pl/ptolemeusz/corridor/
2) Mouse over one of boxes and look at how text looks.

Effect:
In Chrome Canary & Firefox stable text looks as in Chrome.png screenshot; on Safari it's way thinner, as in Safari.png screenshot. Worth noting is that in Chrome stable the bug exists, too, so they had to fix it recently. Nonetheless, in Webkit nightly the bug still exists.
Comment 1 Michał Gołębiowski-Owczarek 2012-11-30 10:00:24 PST
Created attachment 176986 [details]
Webkit Nightly screenshot (in Chrome stable it looks the same)
Comment 2 Michał Gołębiowski-Owczarek 2012-11-30 10:04:00 PST
Chrome stable and Webkit Nightly experience this bug differently, though. In Chrome it's enough to remove the last div, containing two canvases stretching to the entire window and the fonts start to look as intended; in Webkit it's not enough (that's why I didn't prepare a minimal example, I honestly have no idea what's causing the issue :/).
Comment 3 Alexey Proskuryakov 2012-11-30 13:23:37 PST
Is this bug 23364?
Comment 4 Michał Gołębiowski-Owczarek 2012-11-30 14:04:19 PST
It might be, though shouldn't it then start behaving correctly once canvases are removed from the DOM? As it was in Chrome?
Comment 5 Michał Gołębiowski-Owczarek 2012-11-30 14:05:05 PST
BTW, maybe it's worth a shot to ask Chrome people how they dealt with this; I assume they had to patch their Webkit version somehow.