Netscape 8 Breaks IE XML

An anonymous reader writes "Microsoft has alerted users that Netscape's latest browser appears to break the XML rendering capabilities in Microsoft Internet Explorer. Dave Massy, a senior programme manager for IE, warned users in a blog posting that after installing Netscape 8, IE will render XML files as a blank page, including XML files that have an XSLT transformation. What a week for Netscape 8.0; first the browser needed several fixes hours after its release, then it was discovered that without IE installed, Netscape 8.0 will not install, and now IE needs Netscape uninstalled to work."

Comments

Does anyone use it?

[coop0030]

I haven't tried out Netscape 8.0 (Firefox is fine with me for now), but what are some reasons people are switching to Netscape 8.0?

Does anyone have any stats on how many people are even using it? What are the website statistics showing?

To me this sounds like Netscape ran into a "too little, too late" situation with their newest iteration of their browser.

Re:Does anyone use it?

[Will2k_is_here]

I work the helpdesk part time at my University.

Users have used Netscape since NS 4 days. They don't feel comfortable trying anything else. NS7.2 tells them they have an outdated browser so they just upgrade. That's why they download it.

You're outta here!

[TripMaster Monkey]

1. Netscape browser needed several fixes hours after its release.
   
2. Netscape browser will not install unless IE is installed.
   
3. Installation of Netscape breaks IE.
   

Back in the day, I was a big Netscape fan, and I waas really hoping that this new release would bring them back as a player, but enough is enough, guys. Three strikes, and you are OUT.

One more thing...
<zealot>
Firefox rules...IE sucks...let's fight!
</zealot>

^_^

Re:You're outta here!

[0x461FAB0BD7D2]

You're thinking that Netscape 8 breaking IE is a flaw, while it's clearly a feature. Hence, #3 is not a strike, it's a home-run.

Finally, IE the way I want it.

[yotto]

*IE needs Netscape uninstalled to work.* /me runs out to install Netscape 8.

Re:Selective Slashdot Acceptance

[TommydCat]

If I recall correctly, your submission came up as a blank screen...

And you're too slow!

[Spy der Mann]

I stopped using Netscape after AOL bought it! Kept using NS4.7 (and later IE), until Firefox appeared.

Repeat after me: Netscape, Is, Now, Just, A, Brand.

Re:And you're too slow!

[Anonymous Coward]

So you're the jerk that makes my boss require me to make netscape 4.7 compatible web pages. :p

Sounds like yet another...

[Anonymous Coward]

instance where an arbitrary and totally meaningless deadline for launch wrecked havoc on software.

Releasing Netscape based on Firefox 1.03 after 1.04 was available with important security fixes was completely idiotic if a key differentiator of Netscape is supposed to be superior security!

And then releasing an updated version within 24 hours based on 1.04 to show the world they could simply have delayed the initial launch by a day in the first place proved their mismanagement (any excuse about changing to 1.04 being complex and delaying the launch too much went out the window).

Now their bragging rights about being able to switch betweeen IE and Firefox rendering is damaged because they didn't test enough to find out if their product breaks existing functionality like displaying XML?

Not Netscape-specific but for software in general...Managers, get a clue, if you don't like deadlines given by engineers then remove features until they can provide timeframes that are acceptable. And you engineers that are too cowardly to say "No, that cannot be done by that time unless we eliminate/postpone some of the requirements" get some balls.

Could it be true?

[jeffphil]

!seineew era sreenigne epacsteN :)

Re:robust opsys layout and design - ayup

[gunnk]

You *could* screw up a *nix system with a bad installer, but it is harder to do for a couple of reasons:

1 -- you usually only need to run the installer as root if you are doing a system-wide installation. If it is just for you it is easier just to install it in your home folder. Personally, I do that fairly often. I have an updated version of whatever I was installing in my space and can fall back on the system-wide version if I foobar it somehow.

2 -- *nix apps are generally more self-contained than Windows apps. The fact that much of the configuration information for Windows programs resides in the registry is just asking for problems. For example:

If program A uses protocol X and program B does so also, installing B may change registry entries concerning protocol X so that they match its needs. Program A stops working with protocol X.

The *nix tradition of self-contained configuration files avoids the collisions that can arise in the registry.

So again, YES, it is possible for an installer to completely wreck a *nix box BUT it is much less likely.

No big deal

[dtfinch]

IE already renders a great number of XML pages as blank, without the help of Netscape.