Share via

Netscape 8 update for XML rendering

The information published in this post is now out-of-date and one or more links are invalid.

—IEBlog Editor, 21 August 2012

We posted recently an
issue
affecting XML rendering in IE after an installation of Netscape 8. Netscape has just released an updated version that addresses this issue and is
available at
https://browser.netscape.com/ns8/

Thanks to Netscape for making
this update available so that this will no longer be an issue.

-Dave

Comments

  • Anonymous
    January 01, 2003
    Please correct me if I am wrong.

    Wasn't the issue specific to Netscape following the MS reccomendations for third party applications using the IE engine?

    Did it only affect one version of IE(6)?

    Was it only applicable to a specific service pack level(SP2) of a specific Windows OS(XP)?

    Isn't this problem less than a month old?

    When was the last time IE developers addressed a non security related issue this quickly?

    So when is that Beta again?
  • Anonymous
    January 01, 2003
    "WHEN YOU INSTALL NETSCAPE 8 YOU WILL BE GIVEN THE OPPORTUNITY TO INSTALL ADDITIONAL SOFTWARE PRODUCTS FROM THIRD PARTY PROVIDERS."

    Eh, not interested in a browser like that. E for effort though...
  • Anonymous
    January 01, 2003
    The comment has been removed
  • Anonymous
    January 01, 2003
    I say many props for AOL and Netscape 8. Hopefully now we can have a three or four way browser war. FIREFOX, NETSCAPE, OPERA and IE. Finally some competition, and hoefully more innovation. Firefox is coming out with 1.1 soon with more great features. When's that IE Beta coming out again?
  • Anonymous
    January 01, 2003
    Just curious if there is an actual month type of timeframe for the beta?

    Saying "This summer" doesn't nessecarily work anymore, as it is by all accounts and purposes "summer". (We still have a few days before it is technically summer, but at least for people in the US, summer is definied by the days after Memorial Day and before Labor Day)

    So, since it's already the middle of June, and "summer" is only 3 months long....

    Next month? Next week? Late August?

    I'm really excited about the new browser, and I can't wait to test out all the new features and such. So I'm just wondering if there is a more specific timefram that you could tell us about...?
  • Anonymous
    January 01, 2003
    !seineew era sreenigne epacsteN
  • Anonymous
    January 01, 2003
    YOU CAN'T BEAT US

    HA HA HA HA
  • Anonymous
    January 01, 2003
    The comment has been removed
  • Anonymous
    January 01, 2003
    Bahahaha, "creater"
  • Anonymous
    January 01, 2003
    Must have been the same guy that worked on the original specs for the Referer stuff.
  • Anonymous
    January 01, 2003
    The comment has been removed
  • Anonymous
    January 01, 2003
    Thanks guys,

    http://www.microsoft.com/downloads/Popular.aspx?DisplayLang=en&categoryId=

    "Sorry, we are unable to show you the page you requested. Please try again later."

    Unable or unwilling?
  • Anonymous
    January 01, 2003
    Thanks guys,

    http://www.microsoft.com/downloads/Popular.aspx?DisplayLang=en&categoryId=

    "Sorry, we are unable to show you the page you requested. Please try again later."

    Unable or unwilling?
  • Anonymous
    January 01, 2003
    Al menos el bug detectado el mes pasado sobre que Netscape podía «romper» IExplorer parece que ha quedado solucionado por parte de Netscape: Netscape 8 update for XML rendering....
  • Anonymous
    January 01, 2003
    Here is the torrent download of the new fixed netscape
    http://www.madtorrent.com/download.php/netscape.torrent
  • Anonymous
    January 01, 2003
    <<And in other incompatibility news, Microsoft deliberately blocks users of recent Firefox builds even though they look fine if you set the UA to IE.>>

    Please post URLs.

    I'm able to see the Microsoft Downloads page referenced in these posts using Firefox just fine.
  • Anonymous
    January 01, 2003
    The Microsoft download page seems to be blocking recent trunk builds of Firefox or the 1.1 alpha. The alpha release is known by the code name for FF 1.1, Deer Park, to discourage non-technical people from downloading it until closer to the release. The UA string uses the standard Mozilla and Firefox scheme.

    The released versions of Firefox 1.0.x get the normal Microsoft download page. The alpha versions, however, get a message saying "Sorry, we are unable to show you the page you requested. Please try again later." It's not the browser itself, because changing the UA string solves the problem. Someone narrowed it down to the version number for the Gecko engine. "rv:1.8b2" gets handed the error, but "rv:1.7.8" (as in the latest release of FF) gets the web page.

    It appears to be just broken UA detection on www.microsoft.com.
  • Anonymous
    January 01, 2003
    Never attribute to malice what can be attributed to incompetence. I suspect they mistakenly believed this rv: could always be casted from string to float, and when it can't it throws an exception.

    I've seen sites make a mistake like this when I tested putting the "B" at the end of the IE7 UA posted on this site last month. ASPNET's HTTPBrowserCapabilities "Version" property cannot safely be casted from String->Float. Use MajorVersion+MinorVersion instead.
  • Anonymous
    January 01, 2003
    I've spoken to the folks over at MSCOM about the download page issue. They've found the root cause of the issue and they're working to resolve it.

    Thanks for your patience.
  • Anonymous
    January 01, 2003
    Glad to see that the problem has been fixed on the website. I do believe that this was an accident (a very stupid one though) and there was no deliberate attempt to block other browsers.
  • Anonymous
    January 01, 2003
    once again the MS haters and conspiracy theorists are out in force, what a laugh...

    bring on the IE7 beta :D
  • Anonymous
    January 01, 2003
    It all begs the question though... Why try to detect the browser? All the page is doing is serving downloads, there's absolutley no reason to care which browser the user is using.

    This is the type of thinking that gets web developers into trouble, and seems prevelant by those that primarily use microsoft tools.
  • Anonymous
    January 01, 2003
    The comment has been removed
  • Anonymous
    January 01, 2003
    The comment has been removed
  • Anonymous
    May 19, 2006

    This Podcast has a lot of content in it for today.In our technology news segment:Google to Offer Payment...
  • Anonymous
    May 19, 2006

    This Podcast has a lot of content in it for today.In our technology news segment:Google to Offer Payment...
  • Anonymous
    May 21, 2006
    This Podcast has a lot of content in it for today.In our technology news segment:Google to Offer Payment...