It often looks like the text is made slightly narrower during the transition, then gets a little bolder once the transition has stopped. Try adding these properties to your heading tags or to the whole body:
Firefox, chrome, safari, opera, and ie6.
Webkit font smoothing antialiased safari. In static resources create a new resource. Best results are to use the device's default antialias which is optimized for that device. Enable crisp text on all of mac os by disabling font smoothing in system preferences > general all the way on the bottom.
The antialiasing mode of font smoothing turns this feature off and instead uses whole pixels to render the fonts. Webkit browsers like chrome & safari sometimes add an aliasing effect during a css3 transition. Css property seems to fix it, but obviously only temporarily.
This makes the fonts look thinner, weaker and blurrier because the resolution is now effectively lower than before. } adam perfect points out this already works in the current version of google chrome. It was a welcome to the world of font smoothing.
Ah yes, this is what we want, the sweet spot. Ozzle commented on aug 21, 2018. Webkit font smoothing not working.
} in my subsequent research this isn’t a new technique. For now, it won’t work yet, but put this in your css file, and you’ll see the changes in the next update of safari: Recent versions of webkit, included with safari 5, introduced an unfortunate css option for web developers to override your preferred choice of text smoothing.
I had the exact same problem described in ken avila's post: Switching from subpixel rendering to antialiasing for light text on dark backgrounds makes it look lighter. Let’s have a look at the dramatic difference this makes on osx:
Is not a feature, it's a bug, and font smooth is a css property that should be depreciated. An atomeditor package for crisp readable text on retina displays. } the difference in font presentation with and without font.
Webkit browsers like chrome & safari sometimes add an aliasing effect during a css3 transition. Antialiased is now in apple's global base.css file, effectively degrading text readability on all of apple's web properties, including all of www.apple.com, the itunes store or the mac app store. As on a mac, all of these browsers use the system default.
First, this change allows project creation in a folder with uppercase letters in its name. Oh hey, fixed it with a custom stylesheet in safari. So, on a mac, type looks the same no matter which browser you use.
This is not supported in any version of internet explorer or edge. Display text with jagged sharp edges. Personally, i’ve found the best way to fix this is to force standard antialiasing on the element which is being transformed.
Apply this style to the elements you see getting aliased: See the article in the credits for detailed instructions. Antialiased; is not a feature, it's a bug, and font smooth is a css property that should be depreciated.
David walsh wrote about this back in 2015 with the exact same code block, and it appears as though frameworks like zurb’s foundation has had it in their code base for just about as long. So if you paint on transparency, it's still transparent. I recommend reading this post to learn more about what font smoothing is, but in this post i'll give you the css properties and values you need to know:
There are no browser preferences that affect the way type is antialiased. Having the same issue, and only on some sites. Til safari had that feature.
Webkit for whatever reason likes to make the fonts swap from subpixel to standard antialiasing when doing css transforms. This will work nicely on chrome, safari, and firefox on a macintosh computer. It often looks like the text is made slightly narrower during the transition, then gets a little bolder once the transition has stopped.
That provides the best and most consistent results.