{"id":150,"date":"2012-04-07T20:49:05","date_gmt":"2012-04-07T19:49:05","guid":{"rendered":"http:\/\/sphinx.lamecarlate.net\/?p=150"},"modified":"2018-09-30T18:00:58","modified_gmt":"2018-09-30T17:00:58","slug":"anti-aliasing-not-working-in-chromium","status":"publish","type":"post","link":"https:\/\/informatique.lamecarlate.net\/articles\/anti-aliasing-not-working-in-chromium","title":{"rendered":"Anti-aliasing not working in Chromium"},"content":{"rendered":"
I recently had to use the CSS3 property transform, in its \u00ab\u00a0rotate\u00a0\u00bb version. This property being currently supported by all modern browsers – but with vendor prefixes -, I thought it would be rendered the same anywhere.<\/p>\n
It was not, not really.<\/p>\n
In Chromium, -webkit-transform:rotate(4deg) on a container led to horribly aliased edges for this container. After some research, it appears that it was a WebKit engine bug, not solved for now. Tragedy! Horror! Pickles! Should my design be thrown away?\u00a0No, don’t weep in sorrow: there is a way.<\/p>\n
Others have the same problem: And others know how to solve it:
\nhttp:\/\/stackoverflow.com\/questions\/5078186\/webkit-transform-rotate-pixelated-images-in-chrome<\/a><\/p>\n
\nhttp:\/\/stackoverflow.com\/questions\/6492027\/css-transform-jagged-edges-in-chrome<\/a><\/p>\n