搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

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.