That's funny, I managed to download and build Mozilla source (keeping it up to date using CVS) using a 28.8 modem. I just downloaded the huge source tarball first, converted into a CVS tree, then updated it that way from then onwards. This resulted in a very small nightly download, instead of 8-10MB. Building is easy on Linux using gmake if you just follow the instructions.
Do you expect your Netscape 1.0 browser to be able to handle CSS??
I'd expect my Netscape 1.0 browser to be able to view an HTML page that contains CSS, yes. The pages should still be perfectly usable without CSS (unless the designer is a complete incompetent).
If you don't want to hammer on unstable builds then why on earth are you downloading development software? The builds are clearly marked as being for testing purposes. Running talkback builds involves no extra work on your part, just clicking a submission button when it crashes. The whole point of using beta software is to report bugs/crashes.
If you're not prepared to do that then why on earth are you using beta software? At least have the respect not to moan about it when things don't work, when your machine configuration is obviously the source of the problem, yet you have no interest in improving things as you'd rather winge. Filing a few bug reports and running talkback builds has meant I now have a very stable browser on my machine, in fact on NT4 at work, Mozilla crashes a hell of a lot less than IE does. What can I do about IE's crashes? Nothing.
In fact, I think the IE6 beta has even gone Mozilla's route and can send crash reports.
If it's crappy for you and not for lots of other people, then have you been filing lots of bug/crash reports, or just closing it and moving along. The bugs won't magically go away if you don't actively either 1) file bugs or 2) hammer away on talkback builds to cause as many crashes as you can. 2) is exactly what you should be doing if it regularly crashes for you, then the problem is far more likely to be resolved. That's what I've done in the past everytime I've had a build that crashed on me, and since doing that I've had nothing but extremely stable builds for a long time.
No, it merely downloads the HTML, just likely every graphical browser out there. Unlike graphical browsers though, it doesn't make additional network requests to fetch the inline images referred to by the HTML.
If you can't get the select tag to work in Netscape 6.1, then I dread to think what your HTML must look like. It's hardly rocket science. You can do stuff using CSS with SELECT's in Netscape 6/Mozilla that don't work at all in IE.
Netscape didn't say they were out of the browser business, that was merely the spin put on it by the online media. They actually said they'd no longer be seen as *just* a browser company. There's no slowing in Mozilla development, Netscape 6.1 was just released a few weeks ago, and Netscape and/or Mozilla is likely to be part of a future AOL line-up.
So anything about Netscape being a dead product is just a red herring.
On which planet? IE is no where near as standards complient as Mozilla, I find myself having to work around its bugs far more than Mozilla. At least Netscape 4's bugginess was easy to work around.
The validator is completely up to date, it uses whatever DTD you quote at the top of your documents. It's designed to pick up the kind of mistakes you can make by misunderstanding what is written in the standards. Mozilla for instance has the best CSS support out there, barring none.
I don't believe this for one minute, users want to log in using their own username, and most modern distributions seem to make setting up user accounts one of the first steps. They don't want to log in as root, it's their own machine so they'd rather log in as "bob".
I'm writing this from Mozilla in a 64MB machine (a 233MHz P2) and it works fine. I'm not running the java component though which seems to eat a lot of memory.
I think it's best to leave it as it is, I regularly
download foo.tar.gz files under Linux and wouldn't want them unzipped on download. Of course you could always have a pref related to the filetype.
Well you can use LyX for that, it opens a lot faster than Word. In fact you could probably type your quick document and start the print before Word has started with a blank page;-)
Slashdot Mirror
apt works on Mandrake as well... I changed to using it a few weeks back. It takes a little while to make you system apt friendly, but:
apt-get -f upgrade
will resolve most problems. It doesn't like multiple packages with the same name though, so you'll need to remove any duplicates.
Download the apt rpm. Install it.
Do:
apt-get update
then
apt-get -f upgrade
That's how I now keep my Mandrake up to date.
That's funny, I managed to download and build Mozilla source (keeping it up to date using CVS) using a 28.8 modem. I just downloaded the huge source tarball first, converted into a CVS tree, then updated it that way from then onwards. This resulted in a very small nightly download, instead of 8-10MB. Building is easy on Linux using gmake if you just follow the instructions.
We really need a browser that lets you *selectively* disable Javascript.
It already exists, just doesn't have a fancy GUI for configuration yet
In Mozilla you can disable any javascript method or property on a site by site basis.
So you can disable window.open, OnClose and other annoying methods.
Deny scripts access to data on your browser, screen dimensions etc.
See here for info on how to do it.
Do you expect your Netscape 1.0 browser to be able to handle CSS??
I'd expect my Netscape 1.0 browser to be able to view an HTML page that contains CSS, yes. The pages should still be perfectly usable without CSS (unless the designer is a complete incompetent).
There is a Sierra game interpreter in development for Linux, you should be able to find it somewhere on http://www.happypenguin.org/.
I've never tried it, having no Sierra games, but it may be worth a look.
If you don't want to hammer on unstable builds then why on earth are you downloading development software? The builds are clearly marked as being for testing purposes. Running talkback builds involves no extra work on your part, just clicking a submission button when it crashes. The whole point of using beta software is to report bugs/crashes.
If you're not prepared to do that then why on earth are you using beta software? At least have the respect not to moan about it when things don't work, when your machine configuration is obviously the source of the problem, yet you have no interest in improving things as you'd rather winge. Filing a few bug reports and running talkback builds has meant I now have a very stable browser on my machine, in fact on NT4 at work, Mozilla crashes a hell of a lot less than IE does. What can I do about IE's crashes? Nothing.
In fact, I think the IE6 beta has even gone Mozilla's route and can send crash reports.
If it's crappy for you and not for lots of other people, then have you been filing lots of bug/crash reports, or just closing it and moving along. The bugs won't magically go away if you don't actively either 1) file bugs or 2) hammer away on talkback builds to cause as many crashes as you can. 2) is exactly what you should be doing if it regularly crashes for you, then the problem is far more likely to be resolved. That's what I've done in the past everytime I've had a build that crashed on me, and since doing that I've had nothing but extremely stable builds for a long time.
No, it merely downloads the HTML, just likely every graphical browser out there. Unlike graphical browsers though, it doesn't make additional network requests to fetch the inline images referred to by the HTML.
If you can't get the select tag to work in Netscape 6.1, then I dread to think what your HTML must look like. It's hardly rocket science. You can do stuff using CSS with SELECT's in Netscape 6/Mozilla that don't work at all in IE.
Netscape didn't say they were out of the browser business, that was merely the spin put on it by the online media. They actually said they'd no longer be seen as *just* a browser company. There's no slowing in Mozilla development, Netscape 6.1 was just released a few weeks ago, and Netscape and/or Mozilla is likely to be part of a future AOL line-up.
So anything about Netscape being a dead product is just a red herring.
On which planet? IE is no where near as standards complient as Mozilla, I find myself having to work around its bugs far more than Mozilla. At least Netscape 4's bugginess was easy to work around.
Rich in Style has a pretty good CSS bug roundup.
Not strictly true, as it relies on two Outlook behaviours: 1) hiding the file extension and 2) automatic execution of attachment that you click on.
I had three copies of it yesterday, all with attachments called something like:
filename.doc.com
If I'd be using Windows & Outlook I would have seen:
filename.doc
The Adobe Acrobat plugin relies on it, it was more for backward compatibility with NS4 than anything else.
As a protest we should use some IE specific javascript to change sites to use white text on a purple background.
Add this to the header:
<script src="ie.js"></script>
Then put this in ie.js:
if (document.all) {
document.write("<style>")
document.write("body {background: purple; color: white}")
document.write("a {color: white}")
document.write("</style>")
}
Much more effective than a meta tag...
Correction:
img[width="468][height="60"] {-moz-opacity: 0.1}
(make image translucent)
img[width="468][height="60"] {display: none}
(make image disappear completely)
Add userContent.css to the chrome directory under your profile, then add this to it:
img[width="468][height="60"] {-moz-opacity: 100%}
It's something like that anyway (search for the CSS Anarchist's Cookbook).
It seems to be okay in Mozilla, I didn't see any question marks.
The validator is completely up to date, it uses whatever DTD you quote at the top of your documents. It's designed to pick up the kind of mistakes you can make by misunderstanding what is written in the standards. Mozilla for instance has the best CSS support out there, barring none.
I don't believe this for one minute, users want to log in using their own username, and most modern distributions seem to make setting up user accounts one of the first steps. They don't want to log in as root, it's their own machine so they'd rather log in as "bob".
> Netscape, Mozilla, Opera
Don't you mean:
Netscape & IE, Mozille & IE, or Opera & IE
IE is integrated into the operating system, you can't just uninstall it (without causing problems).
I'm writing this from Mozilla in a 64MB machine (a 233MHz P2) and it works fine. I'm not running the java component though which seems to eat a lot of memory.
I think it's best to leave it as it is, I regularly
download foo.tar.gz files under Linux and wouldn't want them unzipped on download. Of course you could always have a pref related to the filetype.
Well you can use LyX for that, it opens a lot faster than Word. In fact you could probably type your quick document and start the print before Word has started with a blank page ;-)