Mactype: Firefox dev/nightly 69已删除cairo，无法渲染
gfx.direct2d.disabled已设为true
gfx.canvas.azure.backends和gfx.content.azure.backends手动添加cairo无效
默认参数↓
dev 69
https://ftp.mozilla.org/pub/devedition/releases/69.0b1/win64/en-US/Firefox%20Setup%2069.0b1.exe
nightly 69
https://ftp.mozilla.org/pub/firefox/nightly/latest-mozilla-central/firefox-69.0a1.en-US.win64.installer.exe
yoyocheung
All 38 comments
请等待firefox发布正式版后再确定。
snowie2000
on 3 Jul 2019
@snowie2000 I’m experiencing the same issue with the new Developer edition.
IceMan81
on 3 Jul 2019
Maybe they are changing something that may come back in the stable release. We aren't sure about it.
snowie2000
on 3 Jul 2019
Galuis
on 10 Jul 2019
Oh boy!
IceMan81
on 10 Jul 2019
Great. They learned my way of solving problems: If it can't be solved, remove it.
snowie2000
on 10 Jul 2019
Anyone come across a solution that enables MacType to work with FF 69? So far, I cannot change the azure backend, what ever I set its always skia.
_Didn't really want to comment on a closed ticket, but this was the most relevant one._
IceMan81
on 24 Jul 2019
@IceMan81 They have removed the Cairo backend. So, looks like it is the end of the GDI era of firefox.
snowie2000
on 26 Jul 2019
After upgrading to firefox 68.0.1, my firefox is ruined... completely.
It looks horrible!
looks like they ain't even using directwrite. IE11 works 100 times better than firefox
What are they thinking🤬
snowie2000
on 26 Jul 2019
Since Cairo backend has been disallowed, I changed my Firefox font configuration and enable direct2d for a better look (still not good).
Following https://bugzilla.mozilla.org/show_bug.cgi?id=1557961#c8 suggestion,change gfx.webrender.all=true gfx.webrender.enabled=true, it seems affect mactype rendering (not obvious in the picture).
Hope and wait better rendering change by Mozilla Gfx team.
Edit: DirectWrite is enable in MacType profile.
Galuis
on 27 Jul 2019
Hi @LeeJayl ... Not all MacType profiles turn on Mactype's rendering for DirectWrite. Can you please try one of the following:
ChicoThorn
Clean Sharp
Clean Soft
extratype
mufunyo
And see how you go?
sammilucia
on 27 Jul 2019
@sammilucia Sorry, the previous description is not clear. I've enabled DirectWrite function in profile. My preferences is not good, so it's not obvious in screenshots.
Galuis
on 28 Jul 2019
I've confirmed that starting from firefox 68, MacType (and any other third-party renders) stopped working on firefox, `cause an extra protection of dll injection was added.
What you're going to observe to that the MacType can't apply to firefox.exe (except in registry mode). So, looks like the registry mode is the only way to render firefox so far.
snowie2000
on 29 Jul 2019
After taking hours digging into firefox mozglue.dll, I finally made MacType comply with its standard again. Tray mode is back to work again now.
snowie2000
on 29 Jul 2019
Well, cairo removed in stable 69.
Maybe it's time to move to ESR version.
a0193143
on 3 Sep 2019
After taking hours digging into firefox mozglue.dll, I finally made MacType comply with its standard again. Tray mode is back to work again now.
Is there a mactype update for this to work?
IceMan81
on 3 Sep 2019
Firefox updated itself to v69 today and MacType no longer works.
Fingers crossed this functionality can be restored.
jmbattle0
on 4 Sep 2019
After taking hours digging into firefox mozglue.dll, I finally made MacType comply with its standard again. Tray mode is back to work again now.
Is there a mactype update for this to work?
No patch is needed as it is a bug that raised during my test. The current public version is compatible with all Firefox versions.
@jmbattle0 cairo is removed in the final release and you have to enable DirectWrite support to make it work for Firefox.
snowie2000
on 4 Sep 2019
Closed too soon - I've done everything in this thread and MacType still won't work with Firefox 69!
JimFlasch
on 4 Sep 2019
@snowie2000 Are you enabling Direct Write flags in FF ?
IceMan81
on 6 Sep 2019
Has anyone gotten MacType working in FF 69? If so can you please share your ini, about:config and FF options settings to get it to work?
FrankEBailey
on 8 Sep 2019
Simply use the default.ini and reset everything in about:config to their default values should work
snowie2000
on 8 Sep 2019
@snowie2000 I had to CHANGE about:config and other settings to get MacType to work in Firefox originally (specifically dropping ",skia" from gfx.canvas.azure.backends and gfx.content.azure.backends values and unchecking "use hardware acceleration when available" under General/Performance in the Options menu). Why would resetting them to default make it work now?
JimFlasch
on 8 Sep 2019
It's working here on my Win7 box.
I uninstalled the previous public release of MacType (pretty old), then installed the latest MacType beta. Then I reset the Firefox profile and everything is working fine. I'm currently using the default MacType .ini, but may tweak it later.
jmbattle0
on 9 Sep 2019
@jmbattle0 I now have the latest MacType beta, and it does nothing to make text look better in Firefox.
JimFlasch
on 9 Sep 2019
@JimFlasch They are two different approaches.
With all default values, firefox uses DirectWrite to render its page which is supported by MacType, but not good and customizable enough. That's why we suggested users disable DirectWrite (direct2d) in firefox and switch its backend to cairo which is based on Windows GDI.
However, due to their lack of interests fixing a bug in cairo (https://bugzilla.mozilla.org/show_bug.cgi?id=1559810), the development team decided to remove cairo. Now in firiefox69, the cairo is still there in the option, but no longer works. You have to switch back to Directwrite to make it work in another form.
snowie2000
on 9 Sep 2019
I did - and it's not quite as good as it used to be.
JimFlasch
on 9 Sep 2019
it does nothing to make text look better in Firefox.
it's not quite as good as it used to be.
Which is it?
jmbattle0
on 9 Sep 2019
Text looks a lot more washed out than it did under GDI, though closer examination reveals that it's definitely working with all default settings. I've tried tuning the options for the profile and it doesn't seem to affect the look of the font at all, so that's a real shame.
Is there any hope for increased configurability under FF in future releases of MacType?
FrankEBailey
on 9 Sep 2019
DirectWrite rendering has its own configuration section [DirectWrite] https://github.com/snowie2000/mactype/wiki/DirectWrite-section
snowie2000
on 9 Sep 2019
Thanks snowie2000, that'll teach me to read the documentation more carefully eh! ;)
FrankEBailey
on 9 Sep 2019
Haha, it's just happened to be there. Mactype is not well documented in fact. Shame on me🙈
snowie2000
on 9 Sep 2019
Am I correct in thinking that only the parameters in the DirectWrite section will influence how text appears in Firefox (69)? Changing the rest of the parameters will have no effect, yes?
jmbattle0
on 9 Sep 2019
Found a perfect solution (many thanks to the redditor @TurbanatorUSA). Works on FF 69.0.1 on windows 10.
All you need is to set gfx.font_rendering.cleartype_params.rendering_mode to 5 in about:config.
sur0g
on 1 Oct 2019
Thank you @sur0g ... I'll add it to the wiki!
sammilucia
on 2 Oct 2019
Done, please let me know any corrections (I don't use Firefox 🙄) https://github.com/snowie2000/mactype/wiki/Mozilla-Firefox
sammilucia
on 2 Oct 2019
改了gfx.font_rendering.cleartype_params.rendering_mode之后mactype一样渲染不了,这只是一个微调directwrite的功能
flysn0w
on 3 Oct 2019
I tried setting [gfx.font_rendering.cleartype_params.rendering_mode] to 5, but do not see any difference.
I'm using Firefox 69 under Windows 7 and MacType seems to work okay.
Is this parameter only required for Windows 10?
jmbattle0
on 4 Oct 2019
Related issues
aridzephyr
·
5Comments
l19980623
·
5Comments
kyler719
·
4Comments
MariuzM
·
5Comments
Arrow-Li
·
3Comments
Most helpful comment
Closed too soon - I've done everything in this thread and MacType still won't work with Firefox 69!