Steps to reproduce: 1. Disable hardware acceleration. 2. Restart Firefox. 3. Go to https://dl.dropboxusercontent.com/u/95157096/85f61cf7/ywdw2czlqk.htm. Actual results: The text is not clear or sharp with APZ enabled. Screenshot https://dl.dropboxusercontent.com/u/95157096/85f61cf7/8hm4x1g7ov.png
Regression range: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=738d8ee106fe760c44f54b5f250d0b36a84818c8&tochange=af67b5f73381f154f41ded5926d823709a0ebd08 Regressed by: bug 1157745
This was an intentional choice. We don't support component alpha layers in BasicCompositor, so we had to choose between grayscale text antialiasing + nice APZ scrolling and subpixel text antialiasing + janky main thread scrolling, and we chose the former. And with hardware acceleration you still get all of the good things. We've thought about adding component alpha layer support to BasicCompositor, but it would be a bit of work and it's not clear whether it can perform well.
Hi blinky, I have tested your issue on latest FF release (45.0.2) and latest Nightly build and could not reproduce it. I have disabled HWA and restarted Firefox and there was no difference on how the text is rendered with APZ enabled or disabled. Is this still reproducible on your end ? If yes, can you please retest this using latest FF release and latest Nightly build (https://nightly.mozilla.org/) and report back the results ? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E). Thanks, Paul.
Should disable the protection with the steps in comment 0 to reproduce this bug. See https://dl.dropboxusercontent.com/u/95157096/85f61cf7/z5gqvl1blf.png
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:45.0) Gecko/20100101 Firefox/45.0 Build ID: 20160407164938 I have tested your issue on latest FF release (45.0.2), latest Nightly build (20160417030601) and managed to reproduce it. I have followed the steps from comment 0 and I've disabled the protection on the website in order see any real difference between how the text is rendered. This is more easily noticeable on the latest Nightly(48.0a1) than on the latest release(45.0.2).
Status: UNCONFIRMED → NEW
Ever confirmed: true
First, does forcing on DirectWrite fix this? Set the gfx.font_rendering.directwrite.force-enabled pref to true. I have found that this often improves text. I am curious if it would here, even on the Basic renderer. Second, I often actually intentionally remove RGB antialiasing for image work. I often find that I need to artificially sharpen the text. Is it possible that merely using a sharper greyscale antialiasing would fix the problem without needing component alpha?
You need to log in before you can comment on or make changes to this bug.