Mozilla 0.9.8 branched Tuesday 1/23, giving it more time to sit on a branch than most milestones get (I don't know if this was intentional). If you think you might report bugs, you should use a newer build, since 0.9.8 is effectively two weeks old. Also, 0.9.8 does not include a fix for a bug that caused porn sites to give 404 or 403 errors when users tried to open thumbnail links in separate windows.
Mozilla "nightly" builds always have the latest bug fixes and features, but they also have the latest regressions. For example, build 1/27 could not save files and some builds starting with the evening builds on 1/31 did not support cookies*. Builds after 1/31 use a new "wyciwyg" scheme to handle document.write(), leading to some problems that have not yet been ironed out.
I've been using a morning build from 1/31 for several days and it seems to be free of major regressions. Here are some of the 1/31 morning builds for various operating systems:
WindowsMacMacOSXLinux.
* Don't get a broken build just to be free from cookies. You can turn off cookies in any build by selecting "disable cookies" in the security/privacy preferences.
Be careful. I tried using one of these for porn, and when I woke up, my bed was filled with blinking pop-up ads. It took me half an hour to close them all, and as a result, I was late to my 8AM class. When I got back from class, the bed had started to fill up again, because I had missed a small one that had somehow managed to get inside my pillowcase.
I tried installing Mozilla so I could disable pop-up ads, but it didn't have enough RAM to run Mozilla. So I returned the Nebula and went back to using Mozilla on my computer (with the Pornzilla modifications, of course).
Pornzilla's goal is to turn Mozilla into a great porn browser. I started the project because I felt some important bugs were being neglected by Netscape engineers, even though they do a very good job with other bugs. (Are they not allowed to look at porn while at work?).
The web site includes several modifications to Mozilla that make it better suited for porn browsing and a list of bugs and feature requests related to porn surfing. If you have any other bug numbers or ideas for modifications, please tell me.
(Sorry for the duplicate message. I guess using "preview" before posting isn't a good idea when you've temporarily disabled cookies.)
when the user visits these sites, their back button behavior in most popular browsers is modified as to open multiple pop-ups featuring ads for adult entertainment and gambling sites when pressed, and uses other technology to basically 'trap' the browser until the entire application has to be closed.
Worse, recent Mozilla builds won't even leave pop-up hell using the Exit command if you've enabled the Quick Launch feature. I have filed bug 98923 about this problem. (I used a trick someone mentioned here to disable pop-up ads, so I don't encounter this bug often.)
Slashdot Mirror
Mozilla 0.9.8 branched Tuesday 1/23, giving it more time to sit on a branch than most milestones get (I don't know if this was intentional). If you think you might report bugs, you should use a newer build, since 0.9.8 is effectively two weeks old. Also, 0.9.8 does not include a fix for a bug that caused porn sites to give 404 or 403 errors when users tried to open thumbnail links in separate windows.
Mozilla "nightly" builds always have the latest bug fixes and features, but they also have the latest regressions. For example, build 1/27 could not save files and some builds starting with the evening builds on 1/31 did not support cookies*. Builds after 1/31 use a new "wyciwyg" scheme to handle document.write(), leading to some problems that have not yet been ironed out.
I've been using a morning build from 1/31 for several days and it seems to be free of major regressions. Here are some of the 1/31 morning builds for various operating systems: Windows Mac MacOSX Linux.
* Don't get a broken build just to be free from cookies. You can turn off cookies in any build by selecting "disable cookies" in the security/privacy preferences.
Be careful. I tried using one of these for porn, and when I woke up, my bed was filled with blinking pop-up ads. It took me half an hour to close them all, and as a result, I was late to my 8AM class. When I got back from class, the bed had started to fill up again, because I had missed a small one that had somehow managed to get inside my pillowcase.
I tried installing Mozilla so I could disable pop-up ads, but it didn't have enough RAM to run Mozilla. So I returned the Nebula and went back to using Mozilla on my computer (with the Pornzilla modifications, of course).
Pornzilla's goal is to turn Mozilla into a great porn browser. I started the project because I felt some important bugs were being neglected by Netscape engineers, even though they do a very good job with other bugs. (Are they not allowed to look at porn while at work?).
The web site includes several modifications to Mozilla that make it better suited for porn browsing and a list of bugs and feature requests related to porn surfing. If you have any other bug numbers or ideas for modifications, please tell me.
(Sorry for the duplicate message. I guess using "preview" before posting isn't a good idea when you've temporarily disabled cookies.)
when the user visits these sites, their back button behavior in most popular browsers is modified as to open multiple pop-ups featuring ads for adult entertainment and gambling sites when pressed, and uses other technology to basically 'trap' the browser until the entire application has to be closed.
Worse, recent Mozilla builds won't even leave pop-up hell using the Exit command if you've enabled the Quick Launch feature. I have filed bug 98923 about this problem. (I used a trick someone mentioned here to disable pop-up ads, so I don't encounter this bug often.)