It seems that the latest (or very recent) version of Chrome has introduced a bug causing tab characters in the HTML to not be treated as spaces when text-rendering is set to optimizeLegibility, as it is in Cascade Framework's typography.css file (took me a little time to track this down). See the bug report here:
https://code.google.com/p/chromium/issues/detail?id=446434
For now I am adding the following override to my app:
body,h1,h2,h3,h4,h5,h6 {text-rendering:auto;}
Hopefully the Chromium team will fix the bug; if not I think it might be best to not have optimizeLegibility enabled by default in the typography file, since some developers (such as myself) prefer using tabs rather than spaces for indentation.
It seems that the latest (or very recent) version of Chrome has introduced a bug causing tab characters in the HTML to not be treated as spaces when text-rendering is set to optimizeLegibility, as it is in Cascade Framework's typography.css file (took me a little time to track this down). See the bug report here: https://code.google.com/p/chromium/issues/detail?id=446434
For now I am adding the following override to my app:
Hopefully the Chromium team will fix the bug; if not I think it might be best to not have optimizeLegibility enabled by default in the typography file, since some developers (such as myself) prefer using tabs rather than spaces for indentation.