Tag Archives: chrome

November 17, 2014

Font rendering issues when using CSS transitions in WebKit

A couple of days ago, I was messing about with CSS3 transitions and I noticed that, in Safari at least, text rendering gets messed up for the duration of the transition. WebKit uses sub-pixel anti-aliasing for font smoothing by default; apparently this gets disabled when a GPU-accelerated CSS transition is executed, causing the text to be rendered using “regular” anti-aliasing.

I haven’t found a satisfactory workaround. This Stack Overflow thread recommends using either -webkit-transform: translateZ(0px); or, curiously, explicitly setting sub-pixel smoothing (-webkit-font-smoothing: subpixel-antialiased) even though it should be enabled by default. Either way, you’ll end up with a) thinner (and uglier) fonts even before a transition or b) a slightly less noticeable change—but a change nonetheless—in font rendering during a transition. It’s not an ideal situation.

Feel free to comment on this post if you know of a workaround that eliminates the problem without one having to force regular anti-aliasing.

Update: I found the original bug report, first filed in 2009 (!): https://bugs.webkit.org/show_bug.cgi?id=23364

August 29, 2014
February 6, 2014

It seems like the DirectWrite implementation for the Windows version of Chrome is close to being finished. Thank the gods.

We’re polishing the implementation and making sure it’s ready to ship to all of Chrome’s Windows users. Take a look at the “Blocked on” list for Issue 25541 for what is remaining.

We’re working hard on these and allowing DirectWrite from within the sandbox. When these are all finished we’ll ship it. From there it’ll make its way through Dev Channel, Beta, and finally hit Stable, generally around 10 weeks later, give or take.

March 10, 2010

Firefox may never hit 25 percent market share

Between January and February, Internet Explorer dropped a significant 0.60 percentage points and Firefox slipped 0.18 percentage points. Chrome jumped a sizeable 0.41 percentage points to 5.61 percent of the market while Safari fell 0.06.

December 9, 2009

Ars Technica's hands on with Chrome for Mac

Those just installing Chrome will observe that it’s incredibly fast—as in, Safari levels of fast. This is certainly a plus when many alternate browsers (hi, Firefox) are, well, not. Page renders are quick and keyboard commands can keep up with my 140wpm fingers, something Safari sometimes even has trouble with from time to time.

I’m missing the Safari keyboard shortcuts that allow you to access the bookmarks in the Bookmarks Bar with option-1/2/3 and so on.

December 8, 2009

Chrome for Mac / Safari 4 SunSpider results

Chrome has substantially better JavaScript performance than Safari on my machine.

Chrome beta (full report)

Total:                  601.2ms +/- 5.6%

Safari 4 (full report)

Total:                  699.0ms +/- 2.5%

Significant improvements across nearly all test cases.