Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

搜尋 Mozilla 技術支援網站

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

了解更多

When browsing gallery and switching pictures, there appears to be black frame in between pictures, making flickering effect

  • 1 回覆
  • 0 有這個問題
  • 103 次檢視
  • 最近回覆由 Mishaiger

Hello, when browsing gallery sites, well, i actually only have one in mind (NSFW https://hitomi.la), each time i move to the next picture previous, picture disappears then there is site background, but only for a moment, then the next picture appears, thus creating flickering effect. Its different from slow loading. It only happens on next unloaded picture, meaning, that if i move back and forth between already loaded pictures then everything is fine. Other browsers, Edge and Chrome, doesn't have that problem, they load pictures seamlessly.

I was wondering if i can do something in about:config, but i have no idea what to change. I also tried disabling hardware acceleration, but it made it even worse.

Hello, when browsing gallery sites, well, i actually only have one in mind (NSFW https://hitomi.la), each time i move to the next picture previous, picture disappears then there is site background, but only for a moment, then the next picture appears, thus creating flickering effect. Its different from slow loading. It only happens on next unloaded picture, meaning, that if i move back and forth between already loaded pictures then everything is fine. Other browsers, Edge and Chrome, doesn't have that problem, they load pictures seamlessly. I was wondering if i can do something in about:config, but i have no idea what to change. I also tried disabling hardware acceleration, but it made it even worse.

被選擇的解決方法

After some time of trying various options, i found it. It was indeed about:config setting. Changing image.decode-immediately.enabled to true solved my problem.

從原來的回覆中察看解決方案 👍 0

所有回覆 (1)

選擇的解決方法

After some time of trying various options, i found it. It was indeed about:config setting. Changing image.decode-immediately.enabled to true solved my problem.