Open GoogleCodeExporter opened 8 years ago
Check your prefs, these work here:
gfx.font_rendering.cleartype_params.rendering_mode = 3
gfx.font_rendering.directwrite.enabled = false
Original comment by Silv3rwind
on 7 Oct 2012 at 1:43
gfx.font_rendering.cleartype_params.rendering_mode = 3
gfx.font_rendering.directwrite.enabled = false
not works for me (FF 16.0.1)
but
gfx.direct2d.disabled = true
works.
Original comment by comphi...@gmail.com
on 23 Oct 2012 at 5:35
gfx.direct2d.disabled = true
works for me too. The UI font rendering now looks dreadful, but the page
content renders the fonts perfectly.
Original comment by RicoHol...@gmail.com
on 13 Nov 2012 at 7:52
Don't work with all above.
Original comment by dmit...@podabed.org
on 18 Mar 2013 at 9:07
Setting gfx.direct2d.disabled true worked for me, but this cripples performance
of WebGL rendering such as http://www.unrealengine.com/html5 . That app is
sub-10 fps with direct2d disabled, but well above 60 fps with the default. It
would be nice if MacType could do its thing in Firefox without disabling
direct2d acceleration; WebGL is an increasingly widely-used web technology.
Original comment by jplebreton
on 1 Jul 2013 at 5:56
Is this a bug with Firefox or with MacType?
Original comment by jplebreton
on 13 Dec 2013 at 10:20
Did those settings disappear in FF 26.0 ? I can't seem to find anything about
font rendering nor direct2d in my prefs.js. Issue is still here though.
Original comment by houpert....@gmail.com
on 8 Jan 2014 at 9:01
You'd better not disabled the direct2d because it would cause some issue.
The better solution is enable the direct2d, but disable the hardware
acceleration in options/advanced/general (uncheck the "use the hardware
acceleration when available").
These both work for me.
Original comment by whitesta...@gmail.com
on 10 Feb 2014 at 10:51
Disabling Direct2D does not cause any issues for me other than the large WebGL
performance hit described above.
Enabling Direct2D and disabling hardware acceleration in the options menu
doesn't change perf, stability or MacType rendering for me.
Original comment by jplebreton
on 3 Mar 2014 at 5:07
My Firefox version is 29.0.1 and below setting worked for me in Windows 7 OS
gfx.direct2d.disabled = true
Original comment by rajen...@gmail.com
on 5 Jun 2014 at 2:08
#10, see my comment #5. Disabling direct2D using that setting works, but
Firefox's WebGL performance drops to unusable levels, so it should be
considered a workaround not a fix.
Original comment by jplebreton
on 5 Jun 2014 at 2:21
I have figured out how to separate hw-accelerated rendering and font rendering.
Just tick off the hardware rending option in the settings dialog first.
This will disable both d2d and directwrite.
And then open about:config and set layers.disabled to false.
This will get back d2d acceleration with MacType's font rendering intact.
Original comment by daybreaker12
on 3 Aug 2014 at 7:49
Recently I found that if I run Firefox (31.0) in safe mode, MacType will works
Tried to disable all Addon (extensions and script) manually, but failed to make
Mactype works.
what different between safe mode and disable manual is that safe mode also
disable default theme, so I suspect this is the problem but I haven't found way
to disable default theme.
If anyone know how to disable default theme (not using another theme) I'll try
it.
Original comment by j4.p...@gmail.com
on 27 Aug 2014 at 2:12
I'm on the nightly version. It worked well since some versions and now it
doesn't work anymore.
I've tried with a new fresh profile and it doesn't work as well.
The only solution is the safe mode. :/
Do you know how to fix it?
Original comment by erwann.m...@gmail.com
on 6 Oct 2014 at 7:47
Okay it was the hardware acceleration. I disabled it and it works now.
Original comment by erwann.m...@gmail.com
on 6 Oct 2014 at 7:49
If you need to follow the bugzilla discussion:
https://bugzilla.mozilla.org/show_bug.cgi?id=1062422
Original comment by erwann.m...@gmail.com
on 6 Oct 2014 at 8:03
Original issue reported on code.google.com by
jplebreton
on 24 Sep 2012 at 8:04