Slashdot Mirror

Some of the code nytimes uses:

function pop_me_up(pURL,features){
new_window = window.open
(pURL, "popup_window", features);
new_window.focus();
}

function pop_me_up2(pURL,name,features){
new_window = window.open
(pURL,name,features);
new_window.focus();

There's no need to beat anyone! Just sumbit a Tech Evangelism bug report on Bugzilla for these sites, and Mozilla engineers will cheerfully help the site owner make it work with all browsers.

Mozilla is still unreliable and doesn't render some sites properly (they were designed for IE; live with it),

I'm assuming you mean these w3c compliant pages?

I don't know, Mozilla seems to render them better than IE, in fact IE dosen't..

The fact that some web pages are broken is not a reason to avoid IE, it's a reason to avoid those web pages. Would you use a refrigerator that wasn't designed to store vegetables, or would you say 'wtf those engineers are idoits', I thought so.

You need to do a fresh install. Not only uninstalling Mozilla, but also removing your profile. On Win32, it's under Windows\Application Data. Just delete the Mozilla folder you find there. For the entire archive of releases go to the mozilla.org FTP site.

One of the goals of Perl 6 is to make non-trivial projects possible. That's good. The way it's being done is bad. Perl was once a lightweight, extremely flexible language. Now it's become a huge ugly monster. People wanted OO, so a nasty hack was bolted on top to allow some semblance of it. Now this nasty hack is being expanded. Sure, the code's different, but the basic form is the same. Kludge upon kludge upon kludge; I'd much rather have a nice, clean, pure language (and not one with loads of irritating whitespace thankyou very much).

The same goes for the syntax. All the switching between $, @ and % is really irritating (ask a newbie how to get at the length of the keys array of a hash inside a hash, for example), and the changes proposed for 6 are just making this worse -- it seems that Larry, in his infinite wisdom, wants to prefix every data type with a different hard-to-type character. Perl was only designed for the three data types, and adding more is a mess.

Perl 6 is a complete rewrite, but it keeps all the mess which has accumulated over the previous versions. This is not good. Sure, my const int $var = 27; may look neat (in the same way that, say, Pascal does), but $var isn't entirely constant, or entirely an integer, it's just a hack which makes it sort of behave like one. The whole thing is an exercise in pseudo-computer science masturbation with little real purpose except to please the managers who dislike the one thing that makes Perl special.

On a similar note is regexes. I'm an avid fan of regular expressions simply because a nondeterministic finite automata is far more flexible than linear code. However, Larry must have been smoking that cheap $2 crack when he wrote this. Does he want Perl 6 to be flex or something?

I won't be going on to use 6. It's a nice idea, but it's completely unnecessary. It won't make large projects any easier to manage (the language is still, at heart, an almighty hack -- an impressive one, but still a hack). It won't make OO any cleaner. It won't make development any faster. To put it bluntly, Perl scripts will still look less beautiful than our friend Mr Goatse. I'd prefer to use a language which has always been pure synthesis of science and engineering, not some half-baked imposter.

Perl 6 will be nice, but I'm guessing it will be the end of Perl. It can't do what it wants to do whilst still being based upon a nasty mess. There are now other options, which provide all of Perl's power and none of the mess. Sorry, but *BSD, erm, Perl is dying. Larry is buggering it up the ass without lubricants, just like Shoeboy is doing to Larry's daughter.

Yes I really wish people would look at the source too... if anyone took a look at the source of the example URL for the bug you mention, they might realize that the list item tag was opened and then closed, before the content.

You can't blame the browser for incompetent web design. IE has always been more forgiving in regard to poorly formed html, but that's not necessarily a good thing -- it's just a thumbs up to writing sloppy html.

... is it's standards compliance.
Try the cool demos, using nothing but fully w3c-compliant HTML/CSS code.

Try that with IE. Honestly, IE still won't even support transpartent PNG's, effectively rendering (no pun intended) it useless as a serious web browser. No matter how popular it is.

On the page http://www.mozilla.org/releases/, the download links are broken. They appear to have the wrong filenames, and in addition the files on the FTP server have mispelled names ("install" missing the last "l"). I was able to figure this out but lots of other MacOS users might not - if you value your enthusiastic MacOS fans, get this fixed pronto!

The world's greatest browser took over four years to be made, and you're complaining? I bet you would have complained that Michelangelo couldn't finish a simple roof painting job overnight.

Some things are just worth waiting for.

Mozilla doesn't do gopher very well-- for example, it fails to show information tags (a big nuisance): try publication or floodgap in Moz and another browser and see the difference.

Or maybe you mean like Galeon [sf.net] for those with Gnome. Or maybe Skipstone which is just GTK+ based? Or K-meleon [sourceforge.net] if you are on Windows? There are projects galore out there playing with the Moz codebase.

Even Mozilla uses GTK+ on linux. This is the compile message I received when trying to do a festive compile of Mozilla:

checking for GTK - version >= 1.2.0... no
*** The gtk-config script installed by GTK could not be found.
*** If GTK was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the GTK_CONFIG environment variable to the
*** full path to gtk-config.
*** GTK+ is available from ftp://ftp.gtk.org/pub/gtk
configure: error: Test for GTK failed.

And this when using the options ./configure --disable-toolkit-gtk --disable-gtktes. Too bad. I thought the GUI was indepenent of Qt or GTK.

But don't get me wrong. I'm very happy 1.0 is here. :-)

Did you notice the fireworks on the start page?
Just hover over the parties link.

"C:\Program Files\Mozilla\bin\mozilla.exe" -nosplash

the following is from the above linked page:

Java

Windows and Linux: To run Java applets, you must install the Java Run Time Environment (JRE) plug-in.

Windows: When using installer builds, everything should Just Work without any help.

See the Java section for more details about Java version compatibility.

Windows: If you're using the Installer build and you already have JRE 1.3.0_01 on your system Mozilla should recognize it. If it doesn't recognize it then follow the copy instructions for the zip builds.

If you're using the win32.zip or talkback.zip builds After the JRE is installed on your machine, copy NPJava130_01.dll, NPJava130_01a.dll, NPJava130_01b.dll, NPJava130_01c.dll, and NPOJI610.dll from the install directory (something like C:\Program Files\JavaSoft\JRE\1.3.0_01\bin) to your Mozilla plugins directory (something like C:\Program Files\ Mozilla 1.0 \bin\plugins).

Linux With tar.gz builds on Linux, after the JRE has installed, put a symlink to java2/plugin/i386/ns610/libjava.oji.so in your mozilla1.0 plugins/ directory.

With Linux RPM builds, you must install Java as the root user.

Mac OS: You must have Mac OS Runtime for Java (MRJ) version 2.2 to run Java applets with Mozilla . If you have Mac OS version 8.5 through 8.6, you may need to upgrade your version of MRJ. For an upgrade, you could go to versiontracker's MRJ page.

Hope this helps!

the following is from the above linked page:

Java

Windows and Linux: To run Java applets, you must install the Java Run Time Environment (JRE) plug-in.

Windows: When using installer builds, everything should Just Work without any help.

See the Java section for more details about Java version compatibility.

Windows: If you're using the Installer build and you already have JRE 1.3.0_01 on your system Mozilla should recognize it. If it doesn't recognize it then follow the copy instructions for the zip builds.

If you're using the win32.zip or talkback.zip builds After the JRE is installed on your machine, copy NPJava130_01.dll, NPJava130_01a.dll, NPJava130_01b.dll, NPJava130_01c.dll, and NPOJI610.dll from the install directory (something like C:\Program Files\JavaSoft\JRE\1.3.0_01\bin) to your Mozilla plugins directory (something like C:\Program Files\ Mozilla 1.0 \bin\plugins).

Linux With tar.gz builds on Linux, after the JRE has installed, put a symlink to java2/plugin/i386/ns610/libjava.oji.so in your mozilla1.0 plugins/ directory.

With Linux RPM builds, you must install Java as the root user.

Mac OS: You must have Mac OS Runtime for Java (MRJ) version 2.2 to run Java applets with Mozilla . If you have Mac OS version 8.5 through 8.6, you may need to upgrade your version of MRJ. For an upgrade, you could go to versiontracker's MRJ page.

Hope this helps!

We have two secret weapons: 1. The DOM Inspector; 2. The JavaScript Debugger.

Trust me: no web developer seeing those will want to work without them a moment longer. And that means they will develop in Mozilla/Netscape - using standard HTML and JavaScript - and check in IE6, rather than the other way around.

Thus the Lizard recruits!

Well, if it's of any help, I'm using 1.0rc1 on windows and I installed the calendar from http://mozilla.org/projects/calendar/

What about the IE users? Oh wait, there'd be too many!

(This ad was paid for by Mozilla - The Choice of Web Standards Loving People Everywhere!)

No amount of complaining on my part is going to change any of these sites. On the other hand, most users (my wife for example) hit one site that doesn't work in Opera and decide to go back to IE forever. My big fear is that cluelessness like thiswill continue to allow IE to dominate the browser market. I think that .NET is only going to make this worse.

I found it amusing a year ago. Now it's just an embarrassing bug.

http://mozilla.org/start/1.0/demos.html

have they fixed this one?
bugzilla 92769

oh who cares. i gave up on moz a long time ago. i really like opera, but more and more i'm just using IE. right now i'm using IE on osX and it's pretty nice.

if they've fixed this bug i might try it.

Er. Use the Ximian package of Mozilla. If you just whack a mozilla.org tarball over the top, it could mess up Nautilus (see the Faq question on this topic: # 10.14. I use GNOME. I installed Mozilla from a mozilla.org binary, and now Nautilus isn't working properly).

NOTE: you can't start the profile manager unless Mozilla is fully shut down.

Unix/Linux and Mac, unfortunately, still require you to recompile with your own splashscreen to change it.

Note that you MUST be using SSL news (snews://) on port 563. Use Mozilla, Netscape 6/7, Outlook Express or slrn (those are the newsreaders I know of that do SSL news).

(No, I don't know why.)

Check out FAQ section 11 for a pile of resources for end users, by the way. And the FAQ itself ;-)

Check out FAQ section 11 for a pile of resources for end users, by the way. And the FAQ itself ;-)

Read the FAQ
Summary:
They can't use Netscape's spellchecker, for legal reasons. Mozilla's own one is still in development and not ready for prime-time yet.

If they didn't want to be a mirror, why is there site on the Mozilla mirrors site?

I have a copy at my company as well but I won't publish it to the world, because I'M NOT A MIRROR.

screenshot for the lazy

do yours sort? I've tried numerous times to get them to sort, on two different linux boxen, and one windows 2000 box. No choices actually makes the bookmarks go in any thing close to "order"

Apparently its a known problem. They just dont feel like doing anything about it:
http://bugzilla.mozilla.org/show_bug.cgi?id=139396

June 5th 2002 - Mozilla 1.0 Released

Roughly, about 4.5 years.

Long story short, they can't change the splashscreen because of the legal wrangling necessary. But ANYONE can change the splashscreen to anything by putting at .bmp file named mozilla.bmp in their /mozilla directory.

Personally I think the best ones are here, and no it's not listed on the big list of splashscreens given before.

Long story short, they can't change the splashscreen because of the legal wrangling necessary. But ANYONE can change the splashscreen to anything by putting at .bmp file named mozilla.bmp in their /mozilla directory.

Personally I think the best ones are here, and no it's not listed on the big list of splashscreens given before.

Long story short, they can't change the splashscreen because of the legal wrangling necessary. But ANYONE can change the splashscreen to anything by putting at .bmp file named mozilla.bmp in their /mozilla directory.

Personally I think the best ones are here, and no it's not listed on the big list of splashscreens given before.

I'm using the graphic from here: http://www.mozilla.org/party/2002/flyer.html for my splash screen now.
Thanks for the tip!

Near the end of the release notes, there is the warning

• Do not share a profile between Netscape and Mozilla builds. Doing this can lead to unpredictable results, some of which may include loss of Search settings and preferences and unchecked growth of the Bookmarks file (large enough to freeze your system). It is best to create a new profile for each or manually copy (and change the name) an existing profile.

The bug report itself contains this pathetic comment:

• If you point someone to a door with 'Enter' on it and the handle shocks them when they touch it - maybe they shouldn't do that, but that still makes you a pretty mean bastard.

  that is to say... If Netscape can't use a Mozilla profile(and vice-versa) without causing nasty corruption then it shouldn't be trying. We should offer to import and create a new one without harming the old one - just like we do with other browsers that we like/share users with/ and support but with which we have incompatible profiles. (uhh 4.x)

  Believe me, I'm overjoyed to mark bugs that stem from this behavior as invalid (and I will) but that doesn't strike at the core issue. Lots of users, QA, and developers have spent a ton of time chasing down these demons - no one knew of this incompatibility. Isn't there something to be done?

Near the end of the release notes, there is the warning

• Do not share a profile between Netscape and Mozilla builds. Doing this can lead to unpredictable results, some of which may include loss of Search settings and preferences and unchecked growth of the Bookmarks file (large enough to freeze your system). It is best to create a new profile for each or manually copy (and change the name) an existing profile.

The bug report itself contains this pathetic comment:

• If you point someone to a door with 'Enter' on it and the handle shocks them when they touch it - maybe they shouldn't do that, but that still makes you a pretty mean bastard.

  that is to say... If Netscape can't use a Mozilla profile(and vice-versa) without causing nasty corruption then it shouldn't be trying. We should offer to import and create a new one without harming the old one - just like we do with other browsers that we like/share users with/ and support but with which we have incompatible profiles. (uhh 4.x)

  Believe me, I'm overjoyed to mark bugs that stem from this behavior as invalid (and I will) but that doesn't strike at the core issue. Lots of users, QA, and developers have spent a ton of time chasing down these demons - no one knew of this incompatibility. Isn't there something to be done?

The complete list is at http://www.schnitzer.at/mozparty/

It looks like we'll finally be able to close out Bug #100309.

It's completely new; we put it together in the last few weeks. Kudos to all those in the credits list for their hard work.

Gerv

Start page: http://mozilla.org/start/1.0/

Mozilla doesn't support most IE extensions to the HTML standard. You should report that site in a Tech Evangelism bug to Bugzilla so the site can be fixed.

There's probably a bug or feature that you keep saying to yourself, "I'm sure someone else has noticed/wants this". Most likely someone has. Check out http://bugzilla.mozilla.org.

I'm sure it's almost safe to assume your bug/feature has already been reported.

Now that they have hit 1.0 are versions without talkback going to be availible.

Most likely not, talkback helps them debug!

Have they or will they remove debug information?

The debug menus have been removed since 1.0RC3

The pacakage is still ~10megs for windows. I was hoping to see some reduction for 1.0 since I still use a lowly 56K Modem.

Simple solution, use the Net Installer! It is a 200KB download that lets you choose the options you want, and then download them. If you don't want/need Chatzilla or Mail & News, you can install a smaller package.

As for 10 megs for the full package, that's not big AT ALL! Remember that it comes with Mail & News, an IRC Client, a browser, a WYSIWYG editor, and an address book.

It's completely new, the reviewer's guide for 1.0. Er, it's still being tweaked ;-)

The FAQ is new as well, and already very popular on the user newsgroups and forums. And it will be maintained.

The Start Guide is pretty cool too. Was this around in any form before, or is this completely new?

After downloading Mozilla you can install Java and Flash automatically.

The official bugreport

:-)

Let's party !

I have been using Mozilla almost exclusivly for one year.

Mozilla has been the best browser out there (free, stable, feature rich (tabbed browsing, image blocking, fastest rendering)) for six months.

Why 1.0 is news is beyond me.

Mozilla could be improved by making new windows open faster (although tabbed browsing really helps), and adding many of the thousand of feature requests that are in the bugzilla database. Here are bugs for which I am currently voting. I'd like middle mouse button to open forms in new windows, junkbuster functionality built in, an easy way to switch SMTP servers, and the Reply-To on mail to be set to the person mail was sent to to begin with when replying.

FAQ: http://mozilla.org/start/1.0/faq/

Don't bother looking at these in IE 5.0, its PNG support is rubbish.