search

phamquy / mactype

Automatically exported from code.google.com/p/mactype
2 stars 0 forks source link

MacType doesn't affect Firefox font rendering #27

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. run MacType on a 64-bit Windows 7 machine.
2. run Firefox (version 14 or 15)

What is the expected output? What do you see instead?

Fonts do not get MacType rendering the way other applications do.

What version of the product are you using? On what operating system?

MacType 1.2012.0406.0 on 64-bit Windows 7 service pack 1.  Most recent (past 
year) versions of Firefox seem to exhibit this problem.

Original issue reported on code.google.com by jplebreton on 24 Sep 2012 at 8:04

GoogleCodeExporter commented 9 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

GoogleCodeExporter commented 9 years ago 

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

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
Don't work with all above.

Original comment by dmit...@podabed.org on 18 Mar 2013 at 9:07

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
Is this a bug with Firefox or with MacType?

Original comment by jplebreton on 13 Dec 2013 at 10:20

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
#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

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
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

kud commented 8 years ago

Doesn't work anymore with the latest Firefox 51.x.

Fironet commented 7 years ago

Disabling direct2d no longer works as of v52.0a2 Developer version of Firefox. Last known compatible version was v51.0.0.6162.

The bug linked above is marked Wontfix. No idea what changed between 51 and 52 that caused this but I know @kud was on Nightly who had seen this conflict back in September (on IRC), a couple months before it hit Developer.

Any ideas what can be done? The default rendering literally gives me eye aches.

kud commented 7 years ago

gfx.direct2d.disabled;true

and

gfx.content.azure.backends;direct2d1.1,cairo // remove skia here

iambizkit commented 7 years ago

gfx.direct2d.disabled - true helps, but some websites have troubles with fonts. How to fix? FF 47.0.2 1n44sz1

kud commented 7 years ago

image

I think it's not here the problem.

Fironet commented 7 years ago

@kud thank you ever so much, really. Removing skia from the gfx.content.azure.backends value worked perfectly. How did you discover this was the value to change?

kud commented 7 years ago

Seen on another topic/issue. ;)

edphemeria commented 5 years ago

gfx.direct2d.disabled;true

and

gfx.content.azure.backends;direct2d1.1,cairo // remove skia here

@kud's settings still work in 2019 with FF 66.0.3 (x64).

Thanks!