intertwingly

Site now reads:

<meta-http-equiv="X-UA-Compatible" content="chrome=1">

Which is even worse.

And... site is now “corrected”, so perhaps the instant legacy aspects can be contained, but it is still wrong on so many levels.

There’s no hyphen between meta and http-equiv. They’re just overloading IE’s misguided quirksmode switch. As this is an IE plugin, I guess this decision won’t do much harm, because X-UA-Compatible is in IE anyway. An IE without the plugin will probably ignore this meta directive and use DOCTYPE to decide between quirks and standards mode, so maybe it’s even a good thing because it breaks the intended use of X-UA-Compatible.

Wow! That is beautiful. And so “DEVIOUS” as a friend commented. :)

Mozilla planned to do something similar with ScreamingMonkey, but by hooking <script type="application/ecmascript;version=4"> and <script type="application/javascript;version=2">, but that seems to have died with ActionMonkey.

Sigh, and your site has forgotten me again. Maybe a year isn’t long enough for a cookie, given the odds I’ll comment in the same browser in that time.

Bespin commit [Hat tip to Dion Almaer] => validator output

And another

romanandreg: @gesteves do you know this guy?... he linked a tweet made by you :-s => [link]...

brianleroux: @obie For now, I’ll point to @samruby to explain why gframe is evil: [link]...