Will they ever fix font rendering in firefox 4?

[foxfrog]

No hardware acceleration on my machine. Still, FF 4 keeps font smoothing. Even if I switch it off in Ubuntu's preferences (which is only meant for Ubuntu's GUI itself), FF 4 still displays this ClearType-like crap. Makes reading web pages a pain.

[Copa360]

No hardware acceleration on my machine. Still, FF 4 keeps font smoothing. Even if I switch it off in Ubuntu's preferences (which is only meant for Ubuntu's GUI itself), FF 4 still displays this ClearType-like crap. Makes reading web pages a pain.

You have to edit it in etc/fonts/conf.d

Remove the link to etc/fonts/conf.avail/10-hinting-slight.conf and create a link to etc.fonts/conf.avail/10-hinting-full.conf (or medium if you prefer). That seems to be the only way to get Firefox to "conform".

[Sylph]

Still cr*ppy with Lucida Sans Unicode, Georgia...:



Normal look:

[asquithea]

If you say so. I rather like the top version, though I can see you might think it overly blurry if you sit really close to your monitor.

Hasn't this thread rather run its course?

[avada]

If you say so. I rather like the top version, though I can see you might think it overly blurry if you sit really close to your monitor.

Hasn't this thread rather run its course?

That's what I was thinking too. The thin jagged and thin aliased text is a lot harder to read.

I agree with your second suggestion too. Nothing is wrong with the font rendering. One can even change it with about:config settings too, if one wants jagged and aliased text (or grayscale AA). And there is Anti aliasing tuner too. Maybe it add these info to the first post and then close it?

[Virtual_ManPL]

Nothing is wrong with the font rendering.

Wrong.
Font rendering is different compared to how render it system, other browsers and Firefox without HW Acc or Firefox 3.6.

[avada]

Nothing is wrong with the font rendering.

Wrong.
Font rendering is different compared to how render it system, other browsers and Firefox without HW Acc or Firefox 3.6.

Precisely. Its different, not bugged. Also you can set the values to look like GDI...

[Virtual_ManPL]

I wrote different, not bugged.
Also I know that I can use value to look like GDI Classic, but this value should be default.

[avada]

I wrote different, not bugged.
Also I know that I can use value to look like GDI Classic, but this value should be default.

Says you. I disagree. I actually prefer natural symmetric because of the better shape. They chose this kind of rendering because, they think its better. Most users don't even care whether its one or another. If a handfull of users can't stand anything else than GDI that's their problem, its pointless to keep whining about it. Submit a bug (if there isn't one already) and whine there, and don't get surprised when it gets wontfix'd.

Anyway as we both said its different (by their choice) and not bugged, so there is nothing to fix, therefore the thread lost its purpose. No need to keep it open.

[Virtual_ManPL]

You are wrong, because Firefox should render fonts the same with and without HW Acc (like Chrome); if not, it's clearly a bug which need to be fixed ASAP.

I submitted a bug #652141 and for now it isn't wontfixed.
And you are also wrong about that the most users don't care about fonts. Just type Firefox font blur in google.

Natural Symmetric render poorly Asians symbols, so it's not a god idea to make this default.

[Sylph]

If you say so. I rather like the top version, though I can see you might think it overly blurry if you sit really close to your monitor.

Hasn't this thread rather run its course?

It sucks because ClearType is turned off, yet it turns it on?!!?? And it looks hideous.

[BrunoReX]

They chose this kind of rendering because, they think its better.

Bzzzt, wrong!
It's not supposed to look like that, it's an OS bug (and needs to be fixed by Microsoft), and only happens with Hardware Acceleration enabled.

[Sylph]

If you say so. I rather like the top version, though I can see you might think it overly blurry if you sit really close to your monitor.

Hasn't this thread rather run its course?

That's what I was thinking too. The thin jagged and thin aliased text is a lot harder to read.

I agree with your second suggestion too. Nothing is wrong with the font rendering. One can even change it with about:config settings too, if one wants jagged and aliased text (or grayscale AA). And there is Anti aliasing tuner too. Maybe it add these info to the first post and then close it?

And how does one get "jagged and alised text" when changing the parameters doesn't work either?

[Sylph]

They chose this kind of rendering because, they think its better.

Bzzzt, wrong!
It's not supposed to look like that, it's an OS bug (and needs to be fixed by Microsoft), and only happens with Hardware Acceleration enabled.

How is it an OS bug when all other browsers work normally?

[avada]

If you say so. I rather like the top version, though I can see you might think it overly blurry if you sit really close to your monitor.

Hasn't this thread rather run its course?

It sucks because ClearType is turned off, yet it turns it on?!!?? And it looks hideous.

It looks hideous to you. Anyway modify the proper settings, or use anti aliasing tuner to set it to GDI and aliased.

They chose this kind of rendering because, they think its better.

Bzzzt, wrong!
It's not supposed to look like that, it's an OS bug (and needs to be fixed by Microsoft), and only happens with Hardware Acceleration enabled.

You're wrong. It happens when HA is enabled because it supports more than one rendering method and the default is different (arguably better).

And how does one get "jagged and alised text" when changing the parameters doesn't work either?

That's new to me. I only remember a bug that makes it impossible to disable HA. Anyway use AA tuner, it works fine here.

You are wrong, because Firefox should render fonts the same with and without HW Acc (like Chrome); if not, it's clearly a bug which need to be fixed ASAP.

No it shouldn't follow whatever others do. One of the problems of current ff development is that it follows every whim of Chrome. Its not a bug its a choice

I submitted a bug #652141 and for now it isn't wontfixed.
And you are also wrong about that the most users don't care about fonts. Just type Firefox font blur in google.

Wrong about this too. A small group of people keep whining that it doesn't look the same.