Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The information published in this post is now out-of-date and one or more links are invalid.
—IEBlog Editor, 21 August 2012
I haven’t tried the Netscape beta yet, but I have read that it allows users to switch between the Gecko rendering engine (the one used in Firefox) and Internet Explorer’s rendering engine. I think this a good opportunity to write about the Windows Web Browsing Platform (the IE Platform) and its counterpart, the IE Browser.
The Browser is easy to explain. It’s the blue e. It’s a nice presentation (with toolbars, a Favorites menu, etc.) of the IE Platform. The Browser is meant for end-users; the Platform, for developers.
The Platform is the stuff “under the hood” that every Windows application can rely on to (among other things) navigate to and render web pages. One of the goals of the Platform part is to make using the Internet with Windows applications easy for software developers.
The Platform offers a lot of power. Applications can host the rendering engine in order to display rich web content as an integrated part of the application. When I read HTML email in Outlook, or see pages in Windows Media Player or MSN Explorer or the AOL client (among many, many other clients), or read RSS feeds in RSS Bandit (or many other aggregators) that’s the IE platform at work.
The Platform also allows developers of client applications to use the rich HTML rendering capabilities even when full Web browsing capabilities are not needed. For example, many software developers who want to offer their customers an attractive “web-like” first experience after inserting the CD choose to author HTML Applications (HTAs) rather than write a more traditional Windows application. I’ve seen many product tutorials and the like written with this approach.
Another great thing is that about the platform is that when we deliver an IE security update, all of the experiences that build on the platform are updated as well. This makes life easier for both developers and end users.
Applications on Windows have been able to use the IE platform components since IE3. Here’s some sample documentation from 1997 that shows how easy it is to write a web browser in Visual Basic that uses the IE Platform. Of course, many different languages and technologies can host IE platform components. Here’s a sample application from 2004 that uses C# and Visual Studio Express to create a simple tabbed browser.
I look forward to trying the Netscape beta and having pages work the way they do in IE. I’m happy to see another browser built on top of the IE platform to go along with NetCaptor, Maxthon, and these other ones. I’m also looking forward to what Blake and Joe say about the beta.
(The Platform has a lot more to it that I won’t get into here, but it is extraordinarily flexible and extensible. I gave some examples back here. Expect Chris Wilson and Dave Massy will post more about the platform.)
Dean
(edit: editing error removed)
Comments
Anonymous
January 01, 2003
I would think that at this point, using both rendering engines would be unproductive. Aren't we trying to strive for one standard? Being able to write one set of code, and having it display, and act the same in ALL browsers? It seems to me that this is a step back from this goal.
Maybe I am missing something, or not understanding what is meant exactly. If that is the case, please fill me in.Anonymous
January 01, 2003
I wouldn't even try any Mozilla based systems until they rendered stuff like IE. Turns out...FireFox far surpassed that, infact I found out that IE was rendering everyone wrong all along. My basis of comparison was wrong (need standards support to have proper layout in xhtml/css).Anonymous
January 01, 2003
Adam, exactly. The entire point of standards are for...um...standardization!
Microsoft, while an amazing company in 99% of it's endeavors, has failed, probably due to it's own arrogance, by trying to create a "Microsoft way" instead of admitting the existence of standards. I understand why they did that and in certain areas of my life I fall into the same sin. No one is perfect. When it comes down to it, however, it is the standards that are the basis for comparison.
It isn't FireFox and Netscape which are the rebels in this regard, but rather Microsoft. This is extremely ironic because usually Microsoft is the basis for comparison, and the rebels are the Linux weirdos. Like I say though, Microsoft seems to have fallen into the exact sin they preach so harshly against. The tables have completely been turned.
Nonetheless, my loyalty is to Microsoft...just don't even think about making me use Internet Explorer.Anonymous
January 01, 2003
Paragraph 4:
You can write a basic web browser
seems out of place. This point of view is further supported by the lack of punctuation.
I will take this opportunity to make a snide comment - the IE team seem like the CAN'T write a basic web browser. I hope IE7 won't come with serious feature bloat.
I want fast accurate rendering, and nothing more. Make both the platform and the browser fast and lightweight.Anonymous
January 01, 2003
Imo, the Netscape beta is unprofesional garbage. Besides the color scheme (green + orange + white), Netscape will download ~150K worth of files off of the net for use in the ui if the cache is cleared (confirmed via Fiddler). The RSS stuff is understandable, but 31 requests for ping, gif and css files!? Yes, I'm ranting. :)
Back on topic: As far as the dual rendering engines, I think it sounds good on paper, but doesn't work so well in reality. Not counting any standards stuff, any added extention/plug-in/ActiveX functionality that deals with one engine won't work very well in the other. Firefox extentions like Spellbound and Linkification won't be able to access data inside Trident, and IE enhancements like IESpell won't work with Gecko in the same manner. The only real way around this is for the two engines to add some sort of cross-engine hooks or for the add-ons to be remade for both engines. I doubt either is likely. In the odd event that one does exist for both: it may need to be installed twice to work. Wonderful, isn't it? :)Anonymous
January 01, 2003
Thanks for pointing out the editing error. I fixed it.Anonymous
January 01, 2003
Actually, I see his point. Any one can write a basic web browser. That's not a big deal. I remember when intro programming books used to have that as one of their sample projects.
IE as a platform for other applications to partake is a great idea and works like clockwork most of the time. I totally love it for that. Personally I cannot staaaaand PDF e-books, waaaay too hard to use. I love my CHM books...of course they is built upon what he is referring to as the "IE platform". Of course, a platform in THAT regard needs to be fast and lightweight totally...that's why I love my CHM e-books.
As a browser, it's a joke. It's completely inappropriate for usage in a professional or private environment. A web browser should provide a base system with allowances for extensions(i.e. FireFox).Anonymous
January 01, 2003
<blockquote>Another great thing is that about the platform is that when we deliver an IE security update, all of the experiences that build on the platform are updated as well. This makes life easier for both developers and end users.</blockquote>
Not necessarily. Things break and change between updates. Yet because IE is built into Windows you can't have different versions of the rendering engine for different applications. Because I can distribute Gecko (or Presto after licensing) with my app I get to control the upgrade path and compatibility issues.
This (largely) shifts the burden of compatibility onto the IE developers rather than the application developers. This burden hamstrings you when you want to make changes.
It also prevents sysadmins in large enterprise environments deploying IE more quickly. They have to test each web app, instead of just letting webapps use the old engine until 'proven good' in testing and letting the browser use the new engine.
It's an awful, terrible design decision, and you unfortunately have to live with it.Anonymous
January 01, 2003
Bruce, will IE remain ensnared in the OS until the end of time or will IE7 be somewhat of a break from tradition?Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
The second point by ! is a telling one.
However great the development process at Microsoft is, and however fast the turnaround for patching vulnerabilities, sysadmins can't push out new updates for the browser quickly because of the huge testing burden for non-browser applications.
This makes it a security problem.Anonymous
January 01, 2003
It's a shame the Netscape developers think they have been forced to implement the IE rendering engine as a fallback mechanism to cope with all the awful built-for-IE pages out there. I guess that's the result of the monopolistic approach Microsoft took during the browser wars, which we are all paying for dearly.
However, IMO, sites that are built like that don't desrve my business anyway. I'll take my business elsewhere with Firefox or Opera before I, or let Netscape, open IE for me.
Having said that though, it is at least good to see more competition coming back, which will greatly benefit the web as a whole in the future.Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Can we get some more information regarding any updates planned for the editing facilities within the platform? For example, source code preservation while editing?
Thanks and please keep the information coming!Anonymous
January 01, 2003
Blake Ross on Firefox and Beyond » The more things change…Anonymous
January 01, 2003
Gecko is not only embeddable like IE, but also portable platrform.
There are applications using Gecko and browser clones same as with IE.
Identical post about Netscape can be written from Gecko point of view, with the same benefits highlighted + some more.
Opera7 and KHTML have same capabilities and are also embedded/cloned in some applications, although less popular.
Again, wake up IE team! Things that were nice in IE3 aren't anything extra in times when IE9 should already be released.Anonymous
January 01, 2003
It has been nearly five years since I developed the visual themes for Netscape 6 and 7. I remember howAnonymous
January 01, 2003
> As far as the dual rendering engines, I think it sounds good on paper, but doesn't work so well in reality.
I think the method in which it has been implemented is a little short-sighted. By catering to broken web pages in this manner, they aren't doing anything to resolve the issue, thus making themselves dependent upon the Internet Explorer platform.
If they logged each URI that the Internet Explorer compatibility mode was used on, they could compile a list of the most popular broken sites and make the Mozilla standards advocacy far more effective, because they could spend their time targetting the most appropriate places. This would eventually reduce the need for this feature.
They already have the code to do this; the quality feedback agent already "phones home" (at the request of the user, of course).Anonymous
January 01, 2003
Autism blog, web design blog. Left Brain/Right BrainAnonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Just a friendly reminder Dean, you did promise us a post on: "Standards, standards, standards… say something!"
I await eagerly. Thanks.Anonymous
January 01, 2003
Hey creativeHavoc, thanks for the friendly reminder. Sorry for the delay.Anonymous
January 01, 2003
I just love the security warning that pops up in Netscape 8 when you manually switch to the IE rendering engine.
"You have chosen to view this web site using the Internet Explorer display engine. Your setting will be remembered the next time you visit the site. Please be aware that there are known security vulnerabilities with the Internet Explorer display engine."
(Note this doesn't happen when changing it within the standard options dialog, only for the site options that come up by clicking the yellow shield on the tab)
However, I think it's ironic that the default options set netscape.com (and a few other sites) to use the IE rendering engine!Anonymous
January 01, 2003
I think this is a great idea. Until IE becomes standards complient, this browser gives the users the choice to to choose at will what browser they are using. Personally I don't like the way IE renders pages, so I can use Gecko, and when I come across a page that was obviously made for IE and doesn't work with Gecko, I can just switch. Likewise, all of you loyal IE users can switch to Gecko if you want to see what a page would look like if it was being rendered with proper CSS2 and such. Good call on Netscapes part.Anonymous
January 01, 2003
IE engine and ActiveX in Netscape. It will be death of the Internet.Anonymous
January 01, 2003
"I think the method in which it has been implemented is a little short-sighted. By catering to broken web pages in this manner, they aren't doing anything to resolve the issue, thus making themselves dependent upon the Internet Explorer platform."
True, but that falls under the catagory "Standards Stuff." :) However, there's one problem with your idea. If a user primarily goes to sites that need Trident to look right, a large amount of his history can get sent to the evangelism folks via talkback. That could end up as a big privacy issue if the data is misused. Do you trust AOL or their outsourced developers to to use that data correctly? I don't.Anonymous
January 01, 2003
> That could end up as a big privacy issue if the data is misused.
I did consider that, which is why I mentioned that similar things already happen. The important thing is to keep the user in control of what happens - this is the case for talkback at the moment, I see no reason why something like I suggest would be any different.Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
I have a problem implementing a css for netscape 7.02.I tried using the same one which i wrote for IE.But it does't work..
Kindly help..Its URGENT..
THanx in advanceAnonymous
January 01, 2003
"I look forward to trying the Netscape beta and having pages work the way they do in IE."
The reverse would be much more preferable, no?Anonymous
January 01, 2003
D O N O T T R I E D NETCRAP v8 (BETA). Its full of unuser friendly, crapy graphics, no help, and a bootleg copy version of IE mixed into Firefox.
AOL should just sell Netscape out right now!Anonymous
January 01, 2003
"I’m happy to see another browser built on top of the IE platform to go along with NetCaptor, Maxthon, and these other ones."
This comment sounds like a backhanded complement. I use Firefox, so I haven't used Netscape's new beta version, however, I doubt it is "built on top of the IE platform" in the way other skin browsers might be. If Netscape is based on Firefox then this ability is probably implemented as an extension.
In Firefox they have a "View in IE" extension that lets you use a real browswer and pop-up IE when you arrive at the pages that don't render according to standards. Netscape has just taken this idea a step further.Anonymous
January 01, 2003
http://www.xinyy.org/byby/
http://www.xinyy.org/cryp/
http://www.xinyy.org/xingyongpin/
http://www.dry.com.cn/
http://www.blgang.net/
http://www.google456.com/jsj/
http://www.google456.com/sjhf/
http://www.google456.com/jp/
http://www.google456.com/wzjs/
http://www.google456.com/bjwzjs/
http://www.google456.com/mr/
http://www.google456.com/huojia/
http://www.google456.com/blg/
http://www.google456.com/qyzx/
http://www.google456.com/cqsf/
http://www.google456.com/yxzx/
http://www.google456.com/gxsb/
http://www.google456.com/gzsb/
http://www.wwwxin.com/zzy/
http://www.wwwxin.com/xh/
http://www.wwwxin.com/cmp/
http://www.wwwxin.com/az/
http://www.wwwxin.com/bjp/
http://www.wwwxin.com/zl/
http://www.wwwxin.com/liuxue/
http://www.wwwxin.com/hgjq/
http://www.wwwxin.com/jy/
http://www.wwwxin.com/huojia/
http://www.xinyy.org/xgnza/
http://www.xinyy.org/jieshi/
http://www.xinyy.org/jny/
http://www.xinyy.org/dianqie/
http://www.xinyy.org/bjxtgr/
http://www.xinyy.org/bnxtjs/
http://www.xinyy.org/ndy/
http://www.xinyy.org/nxszxtgr/
http://www.xinyy.org/ywz/
http://www.xinyy.org/nvmmjbgr/
http://www.xinyy.org/nkjb/
http://www.xinyy.org/xueniao/
http://www.xinyy.org/jxqlyy/
http://www.xinyy.org/nljs/
http://www.xinyy.org/zgjml/
http://www.xinyy.org/nxmjxtgr/
http://www.xinyy.org/xinlengdan/
http://www.xinyy.org/bjxgr/
http://www.xinyy.org/nxmjxgr/
http://www.xinyy.org/bjxjs/
http://www.xinyy.org/mjwk/
http://www.xinyy.org/dichongbing/
http://www.xinyy.org/yinwan/
http://www.xinyy.org/pgzl/
http://www.xinyy.org/bjxtgrjp/
http://www.xinyy.org/fujianyan/
http://www.xinyy.org/szxtgr/
http://www.xinyy.org/nanke/
http://www.xinyy.org/xcbjb/
http://www.xinyy.org/qlxzs/
http://www.xinyy.org/niaoshijin/
http://www.xinyy.org/nongniao/
http://www.xinyy.org/xuejing/
http://www.xinyy.org/flxjdy/
http://www.xinyy.org/nxbjgr/
http://www.xinyy.org/mjxtgrjb/
http://www.xinyy.org/niaotong/
http://www.xinyy.org/xingbing/
http://www.xinyy.org/meidu/
http://www.xinyy.org/linbing/
http://www.xinyy.org/tangniaobing/
http://www.xinyy.org/shenbing/
http://www.xinyy.org/yangwei/
http://www.xinyy.org/zhaoxie/
http://www.xinyy.org/shizhen/
http://www.xinyy.org/jrsy/
http://www.xinyy.org/yinshibing/
http://www.xinyy.org/aizibing/
http://www.xinyy.org/chunyao/
http://www.xinyy.org/baidianfneg/
http://www.xinyy.org/anai/
http://www.xinyy.org/zigongai/
http://www.xinyy.org/biyun/
http://www.xinyy.org/niupixuan/
http://www.xinyy.org/dianxian/
http://www.xinyy.org/jiebao/
http://www.xinyy.org/dahan/
http://www.xinyy.org/yulinbing/Anonymous
January 01, 2003
The comment has been removedAnonymous
May 29, 2009
PingBack from http://paidsurveyshub.info/story.php?title=ieblog-netscape-8-beta-the-ie-platform-and-the-ie-browserAnonymous
June 09, 2009
PingBack from http://besteyecreamsite.info/story.php?id=1014