Slashdot Mirror

To bypass the problem, just hit reload after it reloads the page.

I attempted to install Netscape PR2, but after 3 secs on the download bar, it closes and dosen't let me read the error message. Even after changing the servers in config.ini it still does it. Well, so much for PR2.

I'm currently downloading the latest nightly Mozilla build, and I'll try it like I do every once in a while. Mozilla is getting there, but I just can't stand the oversized browser buttons. I guess I like when buttons are slick looking and small.

I just never thought I would be passing up the latest Netscape release, whatever version, for Mozilla. I always saw Mozilla as a buggy, unstable, unlikeable browser, but the more and more I try it I'm starting to grab hold. I don't know whats going on over at Netscape, but it certainly isn't working anymore.

Heck, does anyone remember going to the store and finding nice, packaged boxed of Netscape on the shelves? Even though they cost money, it was nice seeing Netscape proudly displayed. Now, if it's not put out by Microsoft, you won't see it there. The only thing I could find locally was Netscape Communicator Browser "tools". What "tools" do people need for a browser?

Well, it's sad to see this but Netscape has dug it's own grave with me. Maybe if they get their head on straight and release something installable and usuable again, I'll try, but for now, I'm headed for the red monster.

--
Scott Miga
suprax@linux.com

For a good summary of the Java Plug-In support status under Linux, check out the bug report here which has lengthy comments from the Sun engineer who owns it.

You might have to wait until M18 or M19. Last I heard, the Sun's Linux JDK 1.3 was supposed to finalize in October.

Mozilla requires glibc 2.1.

The PR2 release is a complete disservice to the mozilla.org community. There are really two products here, the Mozilla browser and the Commercial browser. The Mozilla browser is a very fine product. The Commercial browser is a steaming pile of shit. Unfortunately, Mozilla.org, the makers of the Mozilla browser, are going to get skewered by Slashdot and trade press magazines because the Commercial browser, which is made by AOL, is such a joke.

Why is the commercial browser so lame? From out site of the walls at AOL/Netscape, I can only guess. But I can tell you that as an active tester of the Mozilla browser, Netscape Product Development Team's bug-fixing priorities are infuriating. Hours before the release of this PR2, I filed two "smoketest blocker" bugs. This is the most severe kind of bug, and should have prevented the release of the browser. A blocker is a bug which prevents the browser from passing the defined smoketests. These are tests of basic functionality. Not passing these tests means that the browser is not ready for release.

These two serious bugs were marked, by AOL/Netscape people, as "MOZ ONLY", which essentially means "to hell with you we're releasing the product anyway." Of course, the product is released, and the Linux installer doesn't work at all if you have bash2, and the browser will dump core if you try to load ftp.netscape.com in a particular way.

The quality control process at AOL/Netscape has completely failed. They do not follow the quality guidelines of the Mozilla project, as defined on the Mozilla web site. By releasing the Commercial product in such a sorry state, they have embarrased everyone who works so hard on Mozilla, and I suspect that they have lowered morale across the entire project.

Shame on you Netscape.

The PR2 release is a complete disservice to the mozilla.org community. There are really two products here, the Mozilla browser and the Commercial browser. The Mozilla browser is a very fine product. The Commercial browser is a steaming pile of shit. Unfortunately, Mozilla.org, the makers of the Mozilla browser, are going to get skewered by Slashdot and trade press magazines because the Commercial browser, which is made by AOL, is such a joke.

Why is the commercial browser so lame? From out site of the walls at AOL/Netscape, I can only guess. But I can tell you that as an active tester of the Mozilla browser, Netscape Product Development Team's bug-fixing priorities are infuriating. Hours before the release of this PR2, I filed two "smoketest blocker" bugs. This is the most severe kind of bug, and should have prevented the release of the browser. A blocker is a bug which prevents the browser from passing the defined smoketests. These are tests of basic functionality. Not passing these tests means that the browser is not ready for release.

These two serious bugs were marked, by AOL/Netscape people, as "MOZ ONLY", which essentially means "to hell with you we're releasing the product anyway." Of course, the product is released, and the Linux installer doesn't work at all if you have bash2, and the browser will dump core if you try to load ftp.netscape.com in a particular way.

The quality control process at AOL/Netscape has completely failed. They do not follow the quality guidelines of the Mozilla project, as defined on the Mozilla web site. By releasing the Commercial product in such a sorry state, they have embarrased everyone who works so hard on Mozilla, and I suspect that they have lowered morale across the entire project.

Shame on you Netscape.

The things that annoy me most about mozilla is that the find in page does not work if there are frames present (bug #40583). And there are numerous crash bugs including some with animated gifs (bug #22519).

As I've said before, Mozilla is progressing just fine as far as I'm concerned. I have found no new bugs in several weeks. A few months ago I was finding a new bug every few days. And within the last couple months, many of the bugs that I had on the top of my list have been fixed. Mozilla is even less crashy. I have a relatively stable build from a couple weeks ago that I was able to visit every site that I visit on a daily basis without a single crash (don't flame me if you don't know what an improvement that is). It will only get better from here folks.

The things that annoy me most about mozilla is that the find in page does not work if there are frames present (bug #40583). And there are numerous crash bugs including some with animated gifs (bug #22519).

As I've said before, Mozilla is progressing just fine as far as I'm concerned. I have found no new bugs in several weeks. A few months ago I was finding a new bug every few days. And within the last couple months, many of the bugs that I had on the top of my list have been fixed. Mozilla is even less crashy. I have a relatively stable build from a couple weeks ago that I was able to visit every site that I visit on a daily basis without a single crash (don't flame me if you don't know what an improvement that is). It will only get better from here folks.

Java being missing is not Mozilla's fault: see this bug report

Then I installed the latest beta of KDE2 (which allows you to run konqueror under normal KDE). I am not going back. KDE just seems to have it sorted, and Mozilla just doesn't. All the features that don't work in Moz are there already in Konqueror. Plus, it doesn't slow my machine down to P75 speed. I wish Mozilla well, and I will download M17 for old times sake -certainly on my Windows partition, where its cookie-handling features surpass IE - but I do wonder if this is going to be a success.
----------------------------------
What are the weapons of happiness?

1. ftp://ftp1.netscape.com/pub/netscape6

   ftp://ftp2.netscape.com/pub/netscape6

   ftp://ftp3.netscape.com/pub/netscape6

   ftp://ftp4.netscape.com/pub/netscape6

   ftp://ftp5.netscape.com/pub/netscape6

   ftp://ftp6.netscape.com/pub/netscape6

   ftp://ftp7.netscape.com/pub/netscape6

   ftp://ftp8.netscape.com/pub/netscape6

   FTP sites for Netscape above ftp8 exist -- I'm using ftp13 now -- Netscape recommends ftp1 to ftp8.

Make sure the directory is writeable, Mozilla requires that the person who runs the application have write permission to the directory where Mozilla is installed.

------------------------------------

So, you don't like Netscape, that's fine, go out and find a copy of Opera or something. If you use Internet Explorer, you're being incredibly short-sighted, and you deserve the world you're going to get.

Sorry, but that is incredibly short-sighted. I'm an anti-Microsoft fundamentalist. I don't have any Microsoft products on my machine. But I have to admit that at this moment IE is a better, more stable, more standards-compliant, easier to use browser than anything we've currently got on Linux (except possibly Konqueror, which I hope to try soon). Mozilla M16 is almost as good, but not nearly stable enough.

It's a bad mistake when you're so blinded by your dislike of the opposition that you can't recognise where they actually are doing better stuff than we are.

also, whatever happened to MathML?

I beleive the latest versions of mozilla support MathML. See thier webpage on it here

I think that the best incentive to do a project is to know someone will use it. The students and the teachers should identify the needs for the school/community and from there you could assign projects to fulfill those needs. Also keep in mind that you don't have to go and start doing things from scratch, the students could enhance/improve existing projects, like Mozilla, etc. and the project doesn't have to be strictly on programming, the students could design/implement systems for the use of the school.

1. Rumor #1 (Why the hell am I numbering this twice? Am I writing this in basic? Is Mozilla written in basic?): Mozilla is late.
2. Debunk #1: Mozilla is not late. Despite the fact that we have a timeline for Mozilla, and it's behind schedule, that does not mean it's late. You will note we took the "1.0" off the timeline, thus Mozilla will never be late no matter how many thousands of years it takes us.

3. Rumor #2: It'll never ship. Too much feature creep, too late.
4. Debunk #2: Of course it will ship. Just because, once again, we don't actually have a 1.0 release planned doesn't mean it'll never ship.

5. Rumor #3:They're trying to turn it into an operating system.
6. Debunk #3: No. It's a platform, which apparently is like an operating system but slower and less useful.

7. Rumor #4: It's too flexible. It trues to do too mch. It's too easy for people to hang things off it.
8. Debunk #4: Mozilla is certainly not too flexible. Everyone wants modularity. Ask your mother if she's happy with Internet Explorer. "Hell no," she'll tell you, in between shots of Wild Turkey. "I want a browser with an XUL interface! So I can give it a 'Dawson's Creek' theme!"

9. Rumor #5: It's too slow.
10. Debunk #5: It is most certainly not too slow. When you start it up, it's doing all kinds of complicated things with plugins and modularity your puny brain could never possibly understand. You should be thanking us for it only taking 30 minutes to get going. When you click on a menu, and it takes 4 minutes for it to come down, that's breaking a world record for XML parsing! 4 minutes is fast for all the modularity you get!

11. Rumor #6: It's too bloated.
12. Debuk #6: It's not too bloated! Who wouldn't want to spend a mere 30 megabyte download to get not just a medicore web browser, but a mediocre mail client, mediocre news client, mediocre chat client, and HTML editor that's about as enjoyable as licking pennies! And don't forget...modularity! So people can build all kinds of amazing mediocre functionality into it! Believe me, this is what you want. This is what everyone wants. The Mozilla project will drag you there, kicking and screaming, whether you like it or not. I should probably point out Galleon, to try and excuse the fact that the web browser in Mozilla sucks ("If you're one of those crazy 'hacker types' who wants a custom browser that boots in under an hour...").

13. Rumor #7: Wait, how is all this FUD? Aren't these legitimate arguments?
14. Debunk #7: No. Any and all arguments against Mozilla are wrong and thus automatically FUD.

15. Rumor #8: Aren't you just arguing all this because you're in denial about backing a losing browser/platform/whatever the hell you want to call it?
16. Debunk #8: No. If Mozilla really was lousy, which it is not, I would be able to handle the fact that I've wasted hours and failed to lose my virginity over a mediocre computer program. Really!

Wait! Come back! Let me tell you more about themes!

Uh, guys, M17 still hasn't been released... speaking of bad reporting :-) (I know, I shouldn't nitpick - sorry).

BTW, a clarification: the Mozilla source tree has branched. The M17 / nsbeta2 branch is being stabalized, and should be released fairly soon (speculation). The M18 'unstable' tree is where all the new features are going in. Once M17 has been released, the two trees will probably be merged.

BTW, you can get both pre-M17 and pre-M18 nightly builds from ftp.mozilla.org.

As to the actual story, CNET is just ignorant. Like any company in a capitalist economy, it only exists while there is demand for it to exist. If you make it well known that CNET is biased and inaccurate, the 'proles' will turn to another source for their news. Eventually, people will realize that better news sources exist, and use them instead.

Forget the fact that if the one who submitted this article actually read it, they would realize that at least 1 web site has been created to deal with the topic.

The real question here is why has it now become popular to complain about Mozilla???

Here is my theory...everyone who is complaining either knows what is really going on or doesn't. Those that Don't are not seeing much because they probably don't keep track of the project...they are the ppl that say "me too".

The rest of those complaining know exactly what is going on and waht to take some of the fame for themselves...why???

Mozilla Tinderbox

Check out this link...here is where the builds and descriptions of bug fixes get placed. Anyone who has been watching tinderbox knows that there has been alot of bug fixes in the past few weeks...plus, the tree in now closed for M17.

This means a new Milestone release is pending...now, why are they complaining that Netscape hasn't done anything???

Mozilla Milestones

Well, there you have it. M17 is overdue, the page mentions that it is unlikely that M17 will be released within 2 weeks of 6/28. Now the question is why is there so much fuss about Netscape PRODUCING SOMETHING??? Could it be because the next step is a push to Beta2 for Netscape???

That's right. Within a month of the release of M17, Netscape 6 Beta2 will be released.

Now, read of this what you may, but it sounds to me like a few people want to take the limelight for Netscape releasing Beta2...

Just my $.02 worth, I could be wrong.

Forget the fact that if the one who submitted this article actually read it, they would realize that at least 1 web site has been created to deal with the topic.

The real question here is why has it now become popular to complain about Mozilla???

Here is my theory...everyone who is complaining either knows what is really going on or doesn't. Those that Don't are not seeing much because they probably don't keep track of the project...they are the ppl that say "me too".

The rest of those complaining know exactly what is going on and waht to take some of the fame for themselves...why???

Mozilla Tinderbox

Check out this link...here is where the builds and descriptions of bug fixes get placed. Anyone who has been watching tinderbox knows that there has been alot of bug fixes in the past few weeks...plus, the tree in now closed for M17.

This means a new Milestone release is pending...now, why are they complaining that Netscape hasn't done anything???

Mozilla Milestones

Well, there you have it. M17 is overdue, the page mentions that it is unlikely that M17 will be released within 2 weeks of 6/28. Now the question is why is there so much fuss about Netscape PRODUCING SOMETHING??? Could it be because the next step is a push to Beta2 for Netscape???

That's right. Within a month of the release of M17, Netscape 6 Beta2 will be released.

Now, read of this what you may, but it sounds to me like a few people want to take the limelight for Netscape releasing Beta2...

Just my $.02 worth, I could be wrong.

The message is: Contribute.

Read the FAQ, browse the source, help with a bug, do what you can to help and the product will ship quicker.

Most of the help needed doesn't even require you to be a programer. Helping to narrow the focus of bug reports helps the programer focus on the problem instead of the fluff. It's a huuuge help.

The message is: Contribute.

Read the FAQ, browse the source, help with a bug, do what you can to help and the product will ship quicker.

Most of the help needed doesn't even require you to be a programer. Helping to narrow the focus of bug reports helps the programer focus on the problem instead of the fluff. It's a huuuge help.

The message is: Contribute.

Read the FAQ, browse the source, help with a bug, do what you can to help and the product will ship quicker.

Most of the help needed doesn't even require you to be a programer. Helping to narrow the focus of bug reports helps the programer focus on the problem instead of the fluff. It's a huuuge help.

The message is: Contribute.

Read the FAQ, browse the source, help with a bug, do what you can to help and the product will ship quicker.

Most of the help needed doesn't even require you to be a programer. Helping to narrow the focus of bug reports helps the programer focus on the problem instead of the fluff. It's a huuuge help.

It is GPL after all

No, it's MPL.

If you think that mozilla is wallowing under the problems of feature creep you are doing one of two things. 1) Smoking crack. 2) So uninformed you should be taken out in the streets and beaten with a wet noodle.

In three months of nightlies I have yet to see a new feature come into mozilla. What I have seen is buggy features become working like they should.

Recently skin switching has made its way into mozilla. This feature has been planned for since the beginning of the XPFE project with its XUL and whatnot. Skin switching is the closest thing to a `feature' that I have seen making it into the tree since M16.

Only a few more of what most people term `features' (you people really should go look at BugZilla the bug tracking system for Moz to see what is a new feature and what has been planed for) that are going to make it into moz are proxy auto-config, SVG, MathML and several others that only aren't in the nightlies because the builders don't want to push larger binaries. In fact most of these are almost done, but just have a few bugs to be worked out before they can be released unto the masses.

Remeber, before you open your mouth, keep your facts straight, check out bugzilla to find out what features are `creeping' and what appear to be creeping because you don't bother to adjust your build configuration.

The author is a daily downloader of Moz nighlies and finds it very strange why other people don't think moz is so very cool

--
Eric is chisled like a Greek Godess

If you think that mozilla is wallowing under the problems of feature creep you are doing one of two things. 1) Smoking crack. 2) So uninformed you should be taken out in the streets and beaten with a wet noodle.

In three months of nightlies I have yet to see a new feature come into mozilla. What I have seen is buggy features become working like they should.

Recently skin switching has made its way into mozilla. This feature has been planned for since the beginning of the XPFE project with its XUL and whatnot. Skin switching is the closest thing to a `feature' that I have seen making it into the tree since M16.

Only a few more of what most people term `features' (you people really should go look at BugZilla the bug tracking system for Moz to see what is a new feature and what has been planed for) that are going to make it into moz are proxy auto-config, SVG, MathML and several others that only aren't in the nightlies because the builders don't want to push larger binaries. In fact most of these are almost done, but just have a few bugs to be worked out before they can be released unto the masses.

Remeber, before you open your mouth, keep your facts straight, check out bugzilla to find out what features are `creeping' and what appear to be creeping because you don't bother to adjust your build configuration.

The author is a daily downloader of Moz nighlies and finds it very strange why other people don't think moz is so very cool

--
Eric is chisled like a Greek Godess

If you think that mozilla is wallowing under the problems of feature creep you are doing one of two things. 1) Smoking crack. 2) So uninformed you should be taken out in the streets and beaten with a wet noodle.

In three months of nightlies I have yet to see a new feature come into mozilla. What I have seen is buggy features become working like they should.

Recently skin switching has made its way into mozilla. This feature has been planned for since the beginning of the XPFE project with its XUL and whatnot. Skin switching is the closest thing to a `feature' that I have seen making it into the tree since M16.

Only a few more of what most people term `features' (you people really should go look at BugZilla the bug tracking system for Moz to see what is a new feature and what has been planed for) that are going to make it into moz are proxy auto-config, SVG, MathML and several others that only aren't in the nightlies because the builders don't want to push larger binaries. In fact most of these are almost done, but just have a few bugs to be worked out before they can be released unto the masses.

Remeber, before you open your mouth, keep your facts straight, check out bugzilla to find out what features are `creeping' and what appear to be creeping because you don't bother to adjust your build configuration.

The author is a daily downloader of Moz nighlies and finds it very strange why other people don't think moz is so very cool

--
Eric is chisled like a Greek Godess

Now if you want to take a look at the overall plan here is a layout of the Milestones As you can see they are at the end of what you call the feature creep, when in actuallity they are at the end of the development cycle and headed into bug/hunting performance tuning.

And the last "milestone build" released was M16 --a week late, even, but that's forgivable. That was on (according to Mozilla's site) June 13, 2000.

According to the milestone roadmap you pointed out M17 was supposed to be released three weeks after M16 was released, the end of June and M18 a month later. Where is M17?

This was supposed to be one of the first milestones to push for feature-completeness and optimization. Here's a chance for Mozilla developers to say "OK, we're done innovating, now we push to get our browser ready for prime-time" and they're dropping the ball.

Mozilla has turned into a big "develoeprs-only" party. Everyone talks about "just downloading and using the latest nightly builds" but for the casual end-user this is not an option. Yeah, I've downloaded the latest nightly builds and I haven't seen any of this great stability that everyone else is reporting.

I'm glad that Taco and others can use Mozilla as their daily browser -- wish I could share in the fun.

Jay (=

Now if you want to take a look at the overall plan here is a layout of the Milestones As you can see they are at the end of what you call the feature creep, when in actuallity they are at the end of the development cycle and headed into bug/hunting performance tuning.

And the last "milestone build" released was M16 --a week late, even, but that's forgivable. That was on (according to Mozilla's site) June 13, 2000.

According to the milestone roadmap you pointed out M17 was supposed to be released three weeks after M16 was released, the end of June and M18 a month later. Where is M17?

This was supposed to be one of the first milestones to push for feature-completeness and optimization. Here's a chance for Mozilla developers to say "OK, we're done innovating, now we push to get our browser ready for prime-time" and they're dropping the ball.

Mozilla has turned into a big "develoeprs-only" party. Everyone talks about "just downloading and using the latest nightly builds" but for the casual end-user this is not an option. Yeah, I've downloaded the latest nightly builds and I haven't seen any of this great stability that everyone else is reporting.

I'm glad that Taco and others can use Mozilla as their daily browser -- wish I could share in the fun.

Jay (=

What are they DOING over there??

Check the milestones page , I quote: "M16 - Feature complete check point - the annual cinco de mayo checkpoint and party"

looks like they are partying and can't code for at least a week because of a massive hangover.
---

• Necko!
• Gecko (AKA Next Generation Layout)
• XP Toolkit

• Necko!
• Gecko (AKA Next Generation Layout)
• XP Toolkit

• Necko!
• Gecko (AKA Next Generation Layout)
• XP Toolkit

• Necko!
• Gecko (AKA Next Generation Layout)
• XP Toolkit

This morning (before this article was posted) I downloaded the most recent nightly build and it passed my smoketest. For the first time I was able to visit all the sites I visit on a daily basis (about a dozen of them) without a single crash.

There are still some things that need to be fixed before I throw away netscape:
Find in page does not work with frames.
Still a bit crashy including some on animated gifs

A much shorter list than the 10 or so things that I had on it about 2 months ago.

This morning (before this article was posted) I downloaded the most recent nightly build and it passed my smoketest. For the first time I was able to visit all the sites I visit on a daily basis (about a dozen of them) without a single crash.

There are still some things that need to be fixed before I throw away netscape:
Find in page does not work with frames.
Still a bit crashy including some on animated gifs

A much shorter list than the 10 or so things that I had on it about 2 months ago.

----------------------------------

I mean, take a look at the Mozilla downloads page, for God's sake:

We make binary versions of of Mozilla available for testing purposes only! They are not stable or complete enough for daily usage. We put them here for you to try out and report the bugs you find. Its guaranteed that you'll find bugs. Lots of them.

It is very important that you understand that these binaries are not complete programs. They might crash on startup. They might delete all your files and cause your computer to burst into flames. Our binaries also include time bombs: they will expire, and stop working, 30 days after the date at which they were built.

I can't be the only one craving a crapped-out incomplete time-bombed browser that may or may not destroy every file on my hard drive.

While Netscape's browser share has been slowly sinking like the Titanic, the Mozilla folks have been standing on deck, yelling through their cardboard bullhorns about how unsafe the lifeboats are.

Microsoft's won the browser war, guys. After years of coding for the buggy-as-the-rainforest Netscape, I cringe at the mention of their name, now. They've become an anti-brand. A name I'd rather avoid.

It makes me wonder: Shouldn't big open-source projects like Mozilla include marketers as part of their team? Some sub-group who's job is to responsibly get the word out and get people downloading?

That coulda saved Mozilla.

You are confused. The virtual boy failed because it wasn't as fun to use as the game boy. That, and it can make one feel sick (in a variety of ways!).

IIRC, Pokemon was not released for the virtual boy, but recently there was a TV show which caused siezures in a significant number of children in Japan.

Lastly, only percentage of the population will get sick using goggles. Don't think that because you had a very bad experience that everyone else will too.

-Adam

Posted using last night's Mozilla build! Go Mozilla!

lightweight text mode browser
heavyweight gui browser

jwz has had nothing to do with Mozilla for well over a year. His resignation notice was no April Fool's joke...
*/

Now we can all analyze redundant data packets six times faster! :-)

Sometimes I wish there were a distributed computing project out there that I actually cared about. Maybe we should start a project to scan the space of all 2MB Linux ELF executables until we find one that corresponds to a fast, stable, standards-compliant web browser. The funny thing is, that might actually take less time than Mozilla...

1) The Mozilla project will not stop working on Composer, Mail/News, XUL, the application framework etc. because releasing a product with less functionality than NS 4.x would be a disaster, and they aren't going to rearchitect the whole thing now. If you don't like it, don't whinge - use Galeon.

2) Everyone involved with Mozilla is busting their butt to get Netscape Beta 2 out of the door. They are not sitting around saying "AOL told me to stop working this month."

3) The fact that outside contributors have contributed IRC clients and games written on Mozilla is a demonstration of its power, and people having fun, not an indication of a lack of focus.

4) Don't moan about standards compliance without quoting Bugzilla bug numbers.

5) Mozilla is currently big and slow because it's full of debugging code and no performance or footprint optimisations have been done yet. They will happen, almost full-time, after Netscape Beta 2.

6) There is a 4.x-lookalike UI in the nightly builds. Don't moan about the default skin - it's for testing purposes.

7) Make no comments about NS 6 Pre 1. By Mozilla standards, it's ancient.

8) We all know Netscape 4 sucks. IE 5 is better than it. You can stop making this point. The code is currently in "security bug fix only" mode because all the developers are working on Mozilla.

9) If you want to do something constructive but aren't a ninja coder, check out The QA Help page.

Gerv

What possible contribution can I make to Mozilla?

Loads - check out The QA Help Page or The BugAThon.

Gerv

What possible contribution can I make to Mozilla?

Loads - check out The QA Help Page or The BugAThon.

Gerv

but the Mozilla.org page sure seems like anyone can help out in almost anywhichway. Sounds like OSS at its worst

Have a look at the checkin rules on the tinderbox page - just because everyone is encouraged to contribute doesn't mean any old random code gets checked in!

Gerv

Please refer me to a URL that is standards compliant that doesn't work in Mozilla.

How about: W3C XHTML standard pages not displayed

It IS a free software licence. Don't get me wrong, it is not the best licence by any means, but it is free.

http://www.fsf.org/philosophy/licen se-list.html

"The Mozilla Public License (MPL).
This is a free software license which is not a strong copyleft; unlike the X11 license, it has some complex restrictions that make it incompatible with the GNU GPL. That is, a module covered by the GPL and a module covered by the MPL cannot legally be linked together. We urge you not to use the MPL for this reason."

Mozilla provides a good FAQ on why things have to be the way they do (they are contracturally obligated).

http://www.mozilla.org/MPL/FAQ.html