Created attachment 8443693 [details] Font rendering example User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release) Build ID: 20140605174243 Steps to reproduce: 1. I logged into Twitter 2. Went to my notification area 3. Hovered over the icon of some linked accounts from a retweet. This pops up a small tooltip (bubble) with the name of the account. Actual results: Initial rendering of the font was correct (cleartype) After about 1/2 a second, the font rendering would switch to a bolder type, which looks like greyscale subpixel rendering. See attached image for an example. Of note, if hovering over a similar icon lower on the page, this "flip" doesn't happen. Expected results: Text should be rendered properly and not suddenly "change" === Additional info: Firefox 30.0 release ATI/AMD Radeon HD6870, latest drivers HWA On, Direct3D10, Direct2D in use Windows 7 SP1 with platform update installed DirectWrite version: 6.2.9200.16492
Playing around with different settings, one in particular changes this behavior: Setting layers.force-active to true prevents the "flip" to greyscale, but at the same time also renders the text with incorrect cleartype parameters (seems to "double-up" on the subpixel rendering, causing a slight rainbow effect).
Regression window(m-i) Good: http://hg.mozilla.org/integration/mozilla-inbound/rev/33087122ace7 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/18.0 Firefox/18.0 ID:20120916022601 Bad: http://hg.mozilla.org/integration/mozilla-inbound/rev/6ee831a85d12 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/18.0 Firefox/18.0 ID:20120916033402 Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=33087122ace7&tochange=6ee831a85d12 Regressed by : Bug 788044
Status: UNCONFIRMED → NEW
Ever confirmed: true
Anyone have any idea yet about this? We're now 8 months later with plenty of changes in the rendering engine (OMTC, DX11, etc.), but this still happens in Firefox (36) and nightly.
Does this still reproduce?
I can still reproduce on Windows10 Nightly52.0a1.
Yes, this still reproduces.
You need to log in before you can comment on or make changes to this bug.