为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Disabling hardware acceleration also screws up font anti-aliasing

  • 1 个回答
  • 6 人有此问题
  • 1 次查看
  • 最后回复者为 impy

more options

As in title.

First screenshot shows what happens with hardware acceleration enabled, which looks better, second screenshot shows how it looks aliased with acceleration disabled, with the stroke missing in certain places on very light fonts.

However, when hardware acceleration is enabled, if I open very large images or lots of inline images at a time, the browser window will flash white, all tabs will lose their favicons, and the browser must be restarted. For this reason I'm looking to keep hardware acceleration disabled, but use it (or its method) for rendering fonts only, if such a thing is possible. Alternatively I'd like a fix for hardware acceleration causing such behavior, although that seems more difficult.

Cleartype and font smoothing are both on systemwide. Disabling any of them makes the fonts even worse.

Thanks in advance.

As in title. First screenshot shows what happens with hardware acceleration enabled, which looks better, second screenshot shows how it looks aliased with acceleration disabled, with the stroke missing in certain places on very light fonts. However, when hardware acceleration is enabled, if I open very large images or lots of inline images at a time, the browser window will flash white, all tabs will lose their favicons, and the browser must be restarted. For this reason I'm looking to keep hardware acceleration disabled, but use it (or its method) for rendering fonts only, if such a thing is possible. Alternatively I'd like a fix for hardware acceleration causing such behavior, although that seems more difficult. Cleartype and font smoothing are both on systemwide. Disabling any of them makes the fonts even worse. Thanks in advance.
已附加屏幕截图

被采纳的解决方案

Actually, I fixed the issue. Setting gfx.direct2d.force-enabled to true was all it took.

定位到答案原位置 👍 1

所有回复 (1)

more options

选择的解决方案

Actually, I fixed the issue. Setting gfx.direct2d.force-enabled to true was all it took.