title: Google Chrome text shadow rendering
body: <p>Google Chrome has an extremely annoying defect in its implementation of CSS3 text-shadow. The sub-pixel antialiasing is turned off when text-shadow is applied. No amount of -webkit-font-smoothing will persuade it otherwise. The crude alpha-channel anti-alias leads to shadow intermixing with the letters and this along with the pixelated text ends up producing a very ugly look. This is even more evident if hand writing fonts are used such as Monotype Corsiva <a href="http://www.newfonts.net/index.php?pa=show_font&amp;id=130" rel="noreferrer">http://www.newfonts.net/index.php?pa=show_font&amp;id=130</a></p>
  
  <p>One of the places you can see this clearly is on Twitter - <a href="http://dev.twitter.com/pages/auth" rel="noreferrer">http://dev.twitter.com/pages/auth</a>. The text-shadow is used for text outline there: view the page in Chrome, compare with FF or IE, you will see how bad it is.</p>
  
  <p>The effect gets even worse with smaller text until it renders it completely unreadable. Technical discussion of the issue is available here: <a href="http://www.google.com/support/forum/p/Chrome/thread?fid=5d1c0f2082af0f21000483e9a516d36e&amp;hl=en" rel="noreferrer">http://www.google.com/support/forum/p/Chrome/thread?fid=5d1c0f2082af0f21000483e9a516d36e&amp;hl=en</a></p>
  
  <p>There is a bug submitted in the Chromium project (issue 23440). This bug has been around more than a year and is still not assigned to anybody. Google devs saw it, decided it is not so important and left it to age. It turns out they only fix the "popular" bugs, a practice so lame that it looks impressive! I am very disappointed with Chrome! Web typography and CSS3 are used by more and more people every day to make the web much more beautiful place! It is a shame such issue exists to slow that down.</p>
  
  <p>So, a public effort is needed to get this one fixed. Tell others about this, write in your blogs. You can go at <a href="http://code.google.com/p/chromium/issues/detail?id=23440" rel="noreferrer">http://code.google.com/p/chromium/issues/detail?id=23440</a> and vote for the issue. You can do that by clicking at the star located at top left page side (Some type of Google account required - gmail, etc).</p>
  
  <p>To make things more clear - my question has two goals:</p>
  
  <ol>
  <li>Find a technical workaround.</li>
  <li>Make Google fix the issue in Chrome.</li>
  </ol>
  
  <p>I will vote up every link posted to an article about the issue and mark as accepted the best one tech solution or public effort.</p>