Closed Bug 1358078 Opened 7 years ago Closed 6 years ago

ClearType rendering is still not fixed in esr52.1.0 on Windows XP

Categories

(Core :: Graphics, defect, P3)

52 Branch
defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: eganda, Unassigned)

References

Details

(Whiteboard: [gfx-noted])

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170417065206

Steps to reproduce:

What was considered here: https://bugzilla.mozilla.org/show_bug.cgi?id=1345222

Still represented in the new 52.1.0 ESR. Removing "skia" helps.

It is also a Thunderbird 52.0.1 problem, solution is the same.
Blocks: 1345222
Status: UNCONFIRMED → NEW
Component: Untriaged → Graphics
Ever confirmed: true
Product: Firefox → Core
(In reply to eganda from comment #0)
> User Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Firefox/52.0
> Build ID: 20170417065206
> 
> Steps to reproduce:
> 
> What was considered here:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1345222
> 

I can't judge what is the actual problem from the above link. ni? Masatoshi Kimura to have a look
Flags: needinfo?(VYV03354)
Hm, bug 1345222 will not help if you do not customize ClearType settings.

Unfortunately, I don't think we can write a new patch to fix a WinXP-only bug. Disabling "skia" on WinXP might be the best possible option.
Flags: needinfo?(VYV03354)
As reported above, I quickly resolved this issue by going into about:config

gfx.content.azure.backends

and changing the value to remove skia.

It literally takes 30 seconds. Since Firefox 52 is the end of the line for XP, we don't have to worry about doing this again!

http://sdfox7.com/xp/files/ffox52ct.jpg
Blocks: 1374225
Priority: -- → P3
Whiteboard: [gfx-noted]
We aren't maintaining firefox on windows XP and esr52 is a dead branch.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
(In reply to Sylvestre Ledru [:sylvestre] from comment #4)
> We aren't maintaining firefox on windows XP and esr52 is a dead branch.

This is hilarious. This issue was filed over two years ago. Now Mozilla considers it “resolved” since XP is no longer supported? Doesn’t seem very ethical at the least.
The resolution is actually "Resolved Wontfix". This means that yes, we had this bug but we decided not to fix it.
You need to log in before you can comment on or make changes to this bug.