Nasty Degradation Issue in Google Chrome

[infinality]

I just updated from Google Chrome stable 13 to stable 14, and noticed this:

http://code.google.com/p/chromium/issue ... stone%20OS

I had seen it in the beta and unstable builds before, but "assumed" it would be fixed prior to making it to stable. Well, I was wrong. I've spent the last hour trying to revert to the old version, but they don't keep those available anymore. So, I had to restore from backup. In addition to the issue I described there, you may also notice that the left and right sides of certain letters are chopped off. It's a damn mess, and Chrome is my main browser, so it sucks.

If you use chrome and/or are annoyed by this, politely confirm at the link above that this is an issue you experience as well, as I'd like to get to the bottom of this ASAP. I'm cloning Chromium git at the moment to see if I can figure out what is happening.

[infinality]

Another one that's been dragging on for a year is this:
http://code.google.com/p/chromium/issue ... l?id=53785

It really could be a Webkit issue (as the last one could be too), as I don't really know how all that stuff works. I know this one also affects Qt from experience, but also from seeing it at one of these links:

https://lists.webkit.org/pipermail/webk ... 05377.html
http://lists.kde.org/?l=kde-core-devel& ... 313272&w=2
https://bugreports.qt.nokia.com//browse/QTBUG-8642

My un-educated guess is that the matrix stuff got beyond whoever was implementing it, so they skipped it, and very few have noticed (or mentioned it) because it's a relatively obscure fontconfig directive to use.

Today, for me, Google has gotten a FAIL. Their servers were all kinds of slow which ended up causing me to post my first bug 3 times I really like their browser, and stuff in general, but we need to make it not suck!

EDIT: It also bothers me that the first issue (first post) wasn't serious enough in anyone's mind to have been fixed by now. I guess once you start liking the way your fonts render, you see things that other people don't???

[cartman]

I think the real problem is that Chrome's graphics rendering engine Skia not supporting the lcd filtering options, see http://code.google.com/p/chromium/issue ... l?id=29871

[infinality]

That may have something to do with it, but the issue you linked to has been going on for quite awhile it looks like. The issue(s) I am experiencing just started very recently.

[pummarola]

I am glad I am not the only one who noticed this. I fortunately had Chrome 13 installed separately so I am sticking with that for the time being. Chrome used to render text very badly around 2009, which is what I think that older bug report deals with. It got significantly better sometime since then but now with 14 and above it has become ugly in a different way.

The bug report linked in the first post has been merged into http://code.google.com/p/chromium/issues/detail?id=96926 so anyone following this should star or post into that one instead. It may well be in WebKit upstream, too.

[meth]

I don't know whether this is related to what you say but I've been having this problem since forever with Chromium (and that's the only reason I don't use it):

FF:



Chromium:

[pummarola]

Just had some bad luck today when my hard disk failed. Could anyone post Chrome 13, or at the very least libpdf.so/x86_64 from that? I can build Chromium 13, but I'll miss the PDF plugin. Thanks!

[kabamaru]

I thought I was the only one

[infinality]

Here's a zip of my /opt/google/chrome directory. It's from the Chrome 13 RPM:
http://www.infinality.net/files/chrome- ... _64.tar.xz

You may get profile errors if you're going backwards from 14, but it still works fine for me.

[meth]

I'm still having that problem on 13. It's not in all fonts; just some places like <textarea>s and such. The screenshot I posted on this thread is 13, this one is 13 too:



For instance, Opera renders all the fonts the same way, even for dialogs (left: Opera; right: Chromium 13):