Looks like someone at Google thinks a lot like me. They have announced an Internet Explorer plug-in that does just what I proposed in my blog entry from a few months ago.
http://blog.chromium.org/2009/09/introducing-google-chrome-frame.html
Not surprisingly, it doesn't look like Microsoft is too happy about it, although the reasoning behind Microsoft's objection (i.e. it makes IE6 less secure) is anything but logical. Come on MS, you got to be able to come up with something better than that!
A bit more surprising (at least for me), is that Mozilla is not happy about it either. Perhaps they don't like Google beating them to the punch, as Google Chrome Frame is an excellent Trojan-Horse for Google's Chrome browser. Not to mention, it builds name recognition for Google's Chrome OS coming in the near future.
Next stop, Google Chrome OS Frame for IE6?
Showing posts with label the web. Show all posts
Showing posts with label the web. Show all posts
Friday, October 9, 2009
Tuesday, June 16, 2009
IE WebKit Add-On - A Possible Solution for Internet Explorer Compatibility?
As many web developers know, getting web sites working with Microsoft's Internet Explorer (especially IE6) can be frustrating at best. Unfortunately, IE is the most popular browser, so not supporting it is simply not an option.
As the newer standards based HTML 5 web technologies become available on browsers such as Firefox, Safari, and Opera, supporting IE will become an even a larger burden for developers. And in many cases, it is not in the best interest for some large players (Microsoft and Adobe included) to quickly rush adoption of these new standards. The recent InfoWorld article regarding HTML 5 explains aspects of this in detail.
This whole thing got me wondering if a plug-in approach could be used for adding alternative rendering engines into IE itself. All it would take is for someone to create an IE plugin (i.e. BHO or Content Extension) with the open source WebKit rendering engine at it's core. A little bit of redirection magic when IE is detected, sends the user to a page to install and launch the IE WebKit add-on, and we're done. This same approach works for Adobe Flash and Microsoft Silverlight. Why not for viewing HTML 5 documents?
As the newer standards based HTML 5 web technologies become available on browsers such as Firefox, Safari, and Opera, supporting IE will become an even a larger burden for developers. And in many cases, it is not in the best interest for some large players (Microsoft and Adobe included) to quickly rush adoption of these new standards. The recent InfoWorld article regarding HTML 5 explains aspects of this in detail.
This whole thing got me wondering if a plug-in approach could be used for adding alternative rendering engines into IE itself. All it would take is for someone to create an IE plugin (i.e. BHO or Content Extension) with the open source WebKit rendering engine at it's core. A little bit of redirection magic when IE is detected, sends the user to a page to install and launch the IE WebKit add-on, and we're done. This same approach works for Adobe Flash and Microsoft Silverlight. Why not for viewing HTML 5 documents?
Subscribe to:
Posts (Atom)