Bug 1600472 Comment 6 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

We are expecting to lose subpixel AA on _some_ pages where Gecko previously has subpixel AA. This is related to the recent work to integrate WR with native compositor interfaces. The trade off is an expected _significant_ performance and battery life win. Our aim is to still have subpixel AA anywhere that Chrome manages to implement subpixel AA.

Given that, and the comment above - it sounds like we are matching what Chrome does on mail.google.com and also on www.reddit.com, but we are not getting subpixel AA on the google home page, whereas Chrome is - ss that right? If so, I'll start looking at this bug by trying to repro on the google home page.
We are expecting to lose subpixel AA on _some_ pages where Gecko previously has subpixel AA. This is related to the recent work to integrate WR with native compositor interfaces. The trade off is an expected _significant_ performance and battery life win. Our aim is to still have subpixel AA anywhere that Chrome manages to implement subpixel AA.

Given that, and the comment above - it sounds like we are matching what Chrome does on mail.google.com and also on www.reddit.com, but we are not getting subpixel AA on the google home page, whereas Chrome is - is that right? If so, I'll start looking at this bug by trying to repro on the google home page.

Back to Bug 1600472 Comment 6