http://tekkie.flashbit.net/web-20/a-fuss-of-web-20-has-left-acid2-aside Flash technology blog Sat, 22 Nov 2008 08:05:55 +0000 http://wordpress.org/?v=2.5 http://tekkie.flashbit.net/web-20/a-fuss-of-web-20-has-left-acid2-aside#comment-42 Ain Tohvri Thu, 15 Nov 2007 22:22:03 +0000 http://tekkie.flashbit.net/web-20/a-fuss-of-web-20-has-left-acid2-aside#comment-42 <a href="http://tekkie.flashbit.net/tag/acid2" rel="nofollow">Acid2</a> compatible engines + Gecko behave very similarly. I have had no tableless XHTML 1.1 Strict sites falling apart on <a href="http://tekkie.flashbit.net/tag/webkit" rel="nofollow">WebKit</a>, Opera or Firefox but I have had few on IE7. If you look at the core of it and the list of <a href="http://tekkie.flashbit.net/tag/css" rel="nofollow">CSS</a> properties supported it doesn't even come close to WebKit. Acid2 compatible engines + Gecko behave very similarly. I have had no tableless XHTML 1.1 Strict sites falling apart on WebKit, Opera or Firefox but I have had few on IE7. If you look at the core of it and the list of CSS properties supported it doesn’t even come close to WebKit.

]]> http://tekkie.flashbit.net/web-20/a-fuss-of-web-20-has-left-acid2-aside#comment-41 Aaron Thu, 15 Nov 2007 18:50:32 +0000 http://tekkie.flashbit.net/web-20/a-fuss-of-web-20-has-left-acid2-aside#comment-41 Microsoft Workaround Explorer? Please. Every browser requires a couple tweaks to render the way you expect. For instance, I can usually get IE7, IE6, FF and Opera more or less pixel-perfect on the first try, but getting Safari to display things right has always been hell. Being standards-compliant doesn't mean much when it still throws you curveballs (such as font spacing, or how it handles certain DOM elements). To be perfectly honest, this is only because I lack a lot of experience with Safari and I need to lean its quirks better. But IE6 was the only browser that truly needed workarounds to render properly. If you're still using workarounds to support IE7, you're doing it wrong. Microsoft Workaround Explorer? Please. Every browser requires a couple tweaks to render the way you expect. For instance, I can usually get IE7, IE6, FF and Opera more or less pixel-perfect on the first try, but getting Safari to display things right has always been hell. Being standards-compliant doesn’t mean much when it still throws you curveballs (such as font spacing, or how it handles certain DOM elements). To be perfectly honest, this is only because I lack a lot of experience with Safari and I need to lean its quirks better. But IE6 was the only browser that truly needed workarounds to render properly. If you’re still using workarounds to support IE7, you’re doing it wrong.

]]>