Bug 123268

Summary: Position fixed text rendering thinner (Safari 6.1)
Product: WebKit Reporter: newbug
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: UNCONFIRMED    
Severity: Normal CC: bryancrews8719
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Mac   
OS: OS X 10.7   
Attachments:
Description Flags
Demonstrates fixed position font rendering bug
none
Safari font-weight comparison (fixed position) none

newbug
Reported 2013-10-24 06:30:40 PDT
There seems to be a bug causing text within a fixed positioned element to render thinner compared to relative, absolute, or static positions. The ouput is comparible to ( -webkit-font-smoothing:antialiased ) and is only evident within fixed elements.
Attachments
Demonstrates fixed position font rendering bug (745 bytes, text/html)
2013-10-30 09:52 PDT, David Myers 		no flags
Details
Safari font-weight comparison (fixed position) (6.08 KB, image/png)
2013-11-05 22:19 PST, newbug 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
David Myers
Comment 1 2013-10-30 09:52:24 PDT
Created attachment 215518 [details] Demonstrates fixed position font rendering bug As the initial reporter noted, this bug causes text within fixed position elements to be rendered as if they had the following declaration: -webkit-font-smoothing: antialiased; This behavior cannot be overridden. Additionally, I believe this only occurs on non-retina screens. Retina screens appear to render the text correctly.
David Myers
Comment 2 2013-10-30 09:54:22 PDT
Comment on attachment 215518 [details] Demonstrates fixed position font rendering bug It also appears this bug cannot be reproduced in an iframe, so you'll have to open the attachment in a new window.
newbug
Comment 3 2013-10-31 15:48:49 PDT
Recently discovered the following Apple Support thread discussing the same issue. https://discussions.apple.com/message/23585433#23585433
newbug
Comment 4 2013-11-05 22:19:08 PST
Created attachment 216134 [details] Safari font-weight comparison (fixed position)
Note You need to log in before you can comment on or make changes to this bug.