From 1435b362781d251fb5062ec32d003d8466b788e4 Mon Sep 17 00:00:00 2001 From: David DeSandro Date: Thu, 14 Jul 2011 18:16:54 -0400 Subject: [PATCH] docs : help : poor type rendering in webkit --- _posts/docs/2011-12-11-help.mdown | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/_posts/docs/2011-12-11-help.mdown b/_posts/docs/2011-12-11-help.mdown index dbdbf55..c74e45b 100644 --- a/_posts/docs/2011-12-11-help.mdown +++ b/_posts/docs/2011-12-11-help.mdown @@ -13,6 +13,7 @@ toc: - { title: CSS transforms in Opera, anchor: css_transforms_in_opera } - { title: Infinite Scroll with filtering or sorting, anchor: infinite_scroll_with_filtering_or_sorting} - { title: Flash, anchor: flash } + - { title: Poor type rendering in WebKit, anchor: poor_type_rendering_in_webkit } --- @@ -126,3 +127,9 @@ If you do plan on implementing Infinite Scroll with filtering or sorting (which [Using CSS transforms with Flash content is a bit buggy in Safari and Firefox](http://dropshado.ws/post/4085720152/css-transforms-breaking-flash). This is problematic when using Isotope on item elements that contain Flash content like YouTube or Vimeo videos, Flash ads, or Flash audio players. The best way to resolve this issue is to disable CSS transforms by setting the [`transformsEnabled` option](options.html#transformsenabled) to false. + +## Poor type rendering in WebKit + +Type rendering may appear poor in WebKit browsers like Chrome and Safari. This is because of Isotope's activation of hardware acceleration. The solution is to add add a matching background to the item elements. See more: [dropshado.ws - Resolving anti-aliasing on WebKit hardware-accelerated elements](http://dropshado.ws/post/6142339613/resolving-anti-aliasing-on-webkit-hardware-accelerated) + +Activating hardware acceleration in WebKit with 3D CSS transforms changes the way WebKit renders text.