Pale Moon forum

Hi everyone,

I have noticed that since Palemoon auto updated to 19.0.1 x64, I get random areas of text that are fuzzy and not rendered properly.

I took a screen grab of the Sky.com website earlier to show poor text rendering under the pictures >

If I resize the page and reset it again, the text appears normally, but it's becoming irritating now...

Has anyone got a fix for this ?

Thanks

Nigel.

Have tried running in "Safe Mode" with all add-ons disabled - The only difference was the poor text rendering appearing in the bookmarks sidebar, which did not happen before, I am currently testing PM out after doing an uninstall / reinstall (rather than an update).
Will post again if this fixes the issue.

Welcome to the forum! Your rendering question is definitely one for Moonchild's expertise. However I came across this current topic on Mozilla Support (SUMO) Q&A Update to Firefox 19 - Now Text is Hard to Read which sounds/looks very much the same as your problem (and as a Reset did not help that OP rather suggests your uninstall/reinstall is unlikely to change things either), mentions bug #812695 and then suggests either disabling hardware acceleration or going into about:config and setting gfx.content.azure.enabled to false (double click).

In Pale Moon 19.0.1 gfx.content.azure.enabled is set to true but the PMTG (Pale Moon Tweak Guide) says default setting is false - but expect that was written for Pale Moon 15.x - some explanation there too.

Is bug #812695 relevant to your set-up and any joy with SUMO's suggested fixes?

Thanks for the welcome Blacklab,

Firstly, I have to report that so far, the uninstall / reinstall does actually appear to have sorted the issue out.

However, the link that you posted does show the exact issue that I am / was having, so if the issue reappears, I will certainly try the "disable hardware acceleration" fix they suggest in that thread or the about:config setting you posted.

Your second link - Bug #812695 is very interesting, as I am using Windows 7 x64 and IE did recently update to the latest version of IE10 (KB2718695) and this could easily have been the cause of the issue - I really can't remember if IE updated before or after the PM 19.0.1 update, but the updates were only a day or so apart.
One of the fixes shown in Bug #812695 states the following -

Btw, the Workaround in Comment 6 (setting gfx.content.azure.backends;cairo) seems to work and IMHO kind of confirms Comment 0 that only disabling D2D Rendering helps.

I checked for this in PM and found that gfx.content.azure.backends; was still set to "direct2d"
However, the entry "gfx.canvas.azure.backends;" was set to "direct2d,cairo" - whether this makes a difference, i really don't know.
Looking further at the direct2d settings in about:config, It looks like at some point, I had set "gfx.direct2d.disabled;" to "true", so it may be something to do with a combination of the uninstall / reinstall and disabling direct2d in about:config.

I'm not sure whether it's a good thing to have direct2d disabled, but whatever I did seems to have fixed the problem for now.

Many thanks,

Nigel

I have marked the original post as solved - I assume that is right.

Glad your reinstall worked - not what I was expecting - but good news all the same!

Thanks for marking topic [Solved] and thanks also for a full reply - I'm no expert on rendering - but I'm sure Moonchild will read it too!

PS. Placing the [Solved] at front/LH end of title is usual/preferable - not planning to lose any sleep over this though!

As a follow up to this post, I have done some experimenting and the issue is definitely something to do with the direct2d rendering. I tried three setups....

1. Setting gfx.direct2d.disabled to false and gfx.content.azure.backends to Cairo. - No text issues

2. Setting gfx.direct2d.disabled to true and gfx.content.azure.backends to direct2d - No text issues

3. Setting gfx.direct2d.disabled to false and gfx.content.azure.backends to direct2d - The unreadable text problem returns

I'm going to leave my settings as per #1 for now as that was recommended on the bugfix page.

Hope this helps others with this issue,

Nigel

p.s. moved the [Solved} - gotta keep the forum neat