Phillip M. Jones, C.E.T. wrote:
>As far as the web browser goes N6 is standards compatible. Communicator
>4.X isn't.
>
>OTOH: with the exception of allowing for muliple mailboxes and Mail
>accounts. The Communicator still works much better.
>
>The biggest fault is lack of the Location bar in Mail and news in two
>pane mode. (You can't get rid of that %^&*@# IE like side bar so you can
>have much more reading room. IN MOz/N6 in order to switch servers (for
>mail) is to click on sidebar to open select the server then close the sidebar.
>
>Next on the Mac platform plugins are broken.
>
>The applications menu in preferences doesn't work on the Mac Platform.
>
>Moz/N6 doesn't allow for uses of embedded sounds (at least the Mac platform).
>
>If you run across a newsgroup that uses old style layer tags which are
>not allowed in MOZ/N6 the image flash on and off at a rapid rate and
>the only way to get out of the post is to do a restart of the computer
>(again the Mac platform). If someone has embedded the sound the console
>appears but instead of the sound a window appears with raw code. (Mac Platform)
>
>Setting of threading and showing unread messages in email (at least for
>Mac platform) still doesn't work right) They do have it working
>correctly in newsgroups. They don't stick in email though.
>
>Even on a G4-500 with 1.5gb of system RAM its still about 3 times or
>more slower to open up at start even with Communicator having tons of
>Bookmarks, and system having tons of Fonts.
>
>
>If and when they get all the above fixed then it will truely be a
>replacement to Communicator.
>
>But until then i will continue to test Moz and N6. And I will continue
>to use Communicator until verstion 5.9.9.9.9 or until such time as the
>above issues are addressed.
>
>
>Jonathan Wilson wrote:
>
>>What in particular makes 4.x better than 6 for the users?
>>Also, given that netscape is focused on netscape 6, why do they still
>>even bother to support 4.x?
>>
>
Although I have never used Mozilla on Mac, in my experience automatic
plugin detection doesn't work and plugins need to be manually added to
the mozilla/./plugin folder. I forget how you figure out which files
you need to copy in there since I just copy my plugin folder from one
build to another, but I am sure someone else will know... This does not
mean that plugins are 'broken', Mozilla just doesn't know you have them
until you tell him.
