The only place I've seen a report (and fix) about this is right here:
It would be interesting to see exactly what is causing the bug...
To quote from kenbodensteiner's fix in that thread:
|OK to fix this issue uninstall Netscape and then |
Navigate to the following:
Highlight and right-click the node titled "xml" and select delete.
Restart your browser and you should be good-to-go.
Good to go unless you re-install Netscape 8, that is. Apparently the new browser messes with the Windows registry and will over-write the above change if you leave it installed.
What is going on here? I understand that AOL outsourced the development of Netscape 8 to a third party. This does not look good very for them, does it?
The good news is this should affect less than 10 people world wide ;)
But IE doesn't render XML anyway - it just shows the tree.
"I understand that AOL outsourced the development of Netscape 8 to a third party."
AOL is on the block, time warner is dumping the division from what I read, they've been itching to get that albatross off their necks since they fired all the aol management.
So look for aol in turn to start dumping all unnecessary expenses, they already stopped winamp development, I don't know why they keep releasing Netscape versions, it's getting silly. And if it's true the stuff was outsourced, ouch, no wonder bugs and problems happened, I'd guess it's only a matter of months before this stuff is a memory.
|But IE doesn't render XML anyway - it just shows the tree. |
Yeah it shows the XML doc tree when no style sheet is declared, it will display a transformation if a XSL file is specified.
Hmmm - I can confirm this issue w/ Win 2K Pro, IE 6.0.2800.1106 SP1 Q823353, and Netscape 8.0.1 - IE is blank, Netscape show the tree if no stylesheet is associated.
Is this a problem?
Ya installed the darn thing ... use it! It's not anything MS didn't do, back in the day ...
[Only slightly facaetious.]
Yep - I installed NS8 last week and just tried now viewing an XML in IE - and yes, I just got a blank page.
If you read various xml/xslt feeds in IE this is a real problem. Either you can't use NN8 on the same machine, or you must change your RSS browsing habits, or you must go through the song and dance above, over and over and over again.
I don't think this was an intentional "salvo" from Netscape against IE, just an unintended consequence of their dual rendering engines approach most likely. We'll see how long it takes them to get it all sorted. You can bet MS has already been in touch with AOL ;)
OK - the story hit eWeek now, and AOL confirms it's accurate.
|America Online on Thursday confirmed that a bug in its new Netscape 8 |
Web browser was breaking certain XML configurations in Microsoft's IE.
eWeek Story [eweek.com]
That story also states that the news "broke" on the IE Weblog (that was on May 25) but WebmasterWorld members were wrestling with it as early as May 20. At any rate, according to the article, Netscape/AOL is readying a patch. I'll bet they are!
LOL... when i started my career a lot of years ago, we used to ask What is Internet Explorer? Why people use it when we have netscape?
If NN8 messes with registry it would get even more unpopular now.
Well I always downloaded NN whenever it came up with a release in order to keep a check at teh sites I make and how they look in NN. This time, I wont download it. I dont want to mess up ... :)
Do I signout as - lol.. Happy IE User!?!
Acutally, there a pretty good article [en.wikipedia.org] on it in the Wkikpedia. It's sort of metaphoric, but correct on most of the details.
The relevance of Netscape 8, for now at least, is how well the Netscape ISP service is taking hold - I'm guessing their new ISP customers will be force-fed the browser.
Anyone heard anything recent about the Netscape ISP service? The TV ad campagin is still rolling here in New England.
Netscape 8 now has released a patch in the 8.02 version of the browser - it no longer creates a conflict with IE's xml rendering. Interesting the way the spin war continues.
|AOL spokesman Andrew Weinstein said that while fixing the XML rendering problem, Netscape came across the probable cause: Faulty documentation on IE provided by Microsoft. A Microsoft representative declined to comment. |