On Wed, Feb 3, 2010 at 4:17 PM, Nimish Gautam ngautam@wikimedia.org wrote:
Basically, it would just involve us putting in a meta tag on our pages that would trigger an IE plugin Google wrote, assuming the IE user had that plugin installed. The plugin essentially causes IE to use google's HTML renderer and JS engine, which are much nicer to develop for than IE. This won't really solve IE development issues, but would be a good move in the right direction as far as I'm concerned.
Any thoughts or compelling reasons why this might not be a good thing to do?
The page says "Note: This is an early-stage release, intended for developers and testing." It doesn't sound like it's ready for us to use yet. I've heard anecdotal reports of stability problems (no, no source offhand). Moreover, it's not clear to me whether it would integrate correctly with all IE features. If we do use it, it could only be after significant testing that demonstrated it's actually a clear improvement.
It might be worth making this an opt-in feature now, though. Adventurous IE users can try it out and report whether they like it or not, or if they spot any bugs. If they do, we can tell them to file them with the Chrome Frame team.