AOL Releases Netscape Beta, Based on Firefox
An anonymous reader writes "Netscape has released their new prototype browser for Windows based on Firefox 0.9.3. The prototype's development was outsourced to Mercurial Communications and includes several Netscape specific extensions. The biggest difference from Firefox, however, is the ability to switch to the Internet Explorer rendering engine from within the browser using an IE ActiveX control. The browser is currently available for a limited download."
There are screenshots and comments over at Planet Mozilla.
...they are beta testing a new IE based browser.
Downloading much faster via the Coral Cache Link, so I thought I'd post it.
Henrik Gemal has screenshots here
Struggling to find a day everyone can make? WhenShallWe.com
It's like a horrid mixture of OSX and windows olive-green theme gone horribly wrong... The upper bars look cramped and the top right portion is a mess of buttons and widgets.
No. It's an ActiveX that works only on Windows, so it's not multi platform and can not be included in the base FF code.
I just don't trust anything that bleeds for five days and doesn't die.
I always thought that Firefox was meant to streamline the webbrowsing experience? The first thing that I noticed when installing the browser is that it asked for my zipcode for weather reports. Ugh, no thanks, 90210 here I come. It also asks for a reboot after install. For what? What do I need to reboot after an install of a webbrowser for? What are they installing?
It defaults to ONE ugly screen with a tab opened, a headlines ticker going, a "money" ticker going, and the menu bar on the opposite side of the window than I am used to. There's a "new tab" option on the left side of the browsing area instead of leaving the main tab open there. You think new users are going to like this? I don't.
At least I don't see any AOL icons installed to my desktop or my favorites (yet). They might come after a restart though.
It's nice to see the backing of AOL/Netscape on Firefox. People might recognize those two names before Firefox and they might switch. Especially if it can render the IE-only pages 100%.
In the new Netscape Browser, select the option to render in Netscape mode, and then type windowsupdate.microsoft.com in the url barl. Lo, Windows Update appears and works!
For those that might not know, firefox has an ie extension available for download. It allows you to open the current page in IE. Why may you ask??? Because there are the occasional pages that just don't look right in firefox. Plus, it's a handy tool for designers who are interested to see how there page looks in the two browsers.
Can you link to the Google branded Firefox? All I've seen is a Firefox branded Google, which is different entirely.
How many people can read hex if only you and dead people can read hex?
They did support the Mozilla development environment for a good many years for like 0 profit
Actually did far more than that...
They donated $2 million to the Mozilla Foundation to get them going and willingly donated the mozilla.org domain name, the Mozilla-related trademarks, and related equipment such as the mozilla.org servers, to Mozilla Foundation. They was obliged to do none of this, just having purchased Netscape and got all this along with them.
See also this story.
Beware: In C++, your friends can see your privates!
While this may not be exactly the same thing AOL is using, it's interesting and topical nonetheless:
Mozilla ActiveX Project
Mozilla ActiveX Control
Like it or not, a lot of corporations have at least 1 browser-based ActiveX control that their employees must use. Allowing Mozilla to run these programs would eliminate a major barrier to entry.
The point in supporting IE rendering is that a large number of pages just don't work with Mozilla or refuse to render "correctly". For this reason, some browsers strive for bug-for-bug compatibility with MSIE.
Of course, that isn't to say that these are necessarily good or bad decisions, or that there aren't better solutions out there. Just that it's easy to understand these decisions and the motivations behind them even if you don't necessarily agree with them.
The point in supporting IE rendering is that a large number of pages just don't work with Mozilla or refuse to render "correctly". For this reason, some browsers strive for bug-for-bug compatibility with MSIE.
They don't strive for bug-for-bug compatibility with IE. They design a flashy UI and link the browser functions to mshtml*.dll so that they won't have to do any real work themselves.
There are better screenshots at:
http://gemal.dk.nyud.net:8090/misc/nsb02.png
http://gemal.dk.nyud.net:8090/misc/nsb05.png
http://gemal.dk.nyud.net:8090/misc/nsb06.png
http://gemal.dk.nyud.net:8090/misc/nsb14.png
http://gemal.dk.nyud.net:8090/misc/nsb15.png
I've put up a screenshot, with notes on Flickr. Bash away.