you cannot select a message without displaying it, thus you cannot forward a spam onto Spamcop without Mozilla starting to render it (and fetching any webbugs in it).
Try collapsing the message area (expanding the threadpane to the bottom of the window). You can do this by dragging the splitter or clicking on the splitter's grippy. When the message area is closed it doesn't load the message.
Konqi has been ahead of both Mozilla and IE on it's CSS2 rendering for about 18 months;
I don't know where you get your information but it's clearly wrong. Feel free to state that Konqueror gets you're particular subset of CSS on one particular page you set up but that's a darned small sample from which you make such sweeping statements about CSS support.
http://www.bath.ac.uk/%7Epy8ieh/cgi/listresults. pl ?ID=ETS seems to suggest otherwise and looks to be a little more thorough than your homepage.
This really lessens Mozillas usefulness as a test tool for a web project as you are not guaranteed to see the original source.
And the fact that it's got a JS debugger _with_ JS profiling (ever wonder where your DHTML was spending it's time? Now you can see), it's got a meaningful JS console, it's got the most fully featured DOM inspector (with live DOM analysis) of any free application, it's got the best support for CSS and the DOM of any browser on the planet... None of this matters because you can't conveniently get at original source for some percentage of pages? OK.
--Asa
The RPMs are daily and milestone build contributions from Chris Blizzard. If DEBs are important to you then make builds and contribute them or find someone that can.
//redirect for people with a less than
//version 4 browser
var NS4 = (document.layers);
var IE4 = (document.all);
var ver4 = (NS4 || IE4);
if(!ver4)
location.href= "notsupported.htm";
and hotmail.com works just fine for me on mac, windows and linux mozilla 0.9.7 builds.
steven-ehrbar@home.com said: See the first line on the release page? It says:
"We make binary versions of Mozilla available for testing purposes only!"
netdemonz AT yahoo DOT com said:
That article is old and out of date. Mozilla milestones are meant to be stable releases that can be used as a personal browser.
It is not old and out of date. Mozilla binaries are provided for testing purposes.
THE NEWS WE ALL NEED TO HEAR ABOUT MOZILLA IS THAT AOL AND/OR SUN AND/OR IBM AND/OR EARTHLINK AND/OR the EU AND/OR CHINA or ???????
Amen! I'd love to hear that news. Making Mozilla better gets us closer to hearing something like that. There are lots of ways that you can help to make Mozilla better. See getting involved page for some of them.
I bet they're releasing the software during the Pacific Ocean timezone to avoid the slashdot effect, cowards).
I'm sure you said that with a wink, but in case not I'll tell you why we release software late in the evening on Fridays. It's because we bust our butts all week trying to get it wrapped up before the weekend. If we work hard and luck is with us we get it out late in the day Friday. If we run into unexpected problems then it's sometime the following week. Fortune smiled on us this milestone cycle and I think we've got something really good to offer (and on time too;-)
Um, that's my text. I'm the co-author of the release notes and the originator of the what's new section. I would think that I'm allowed to post that here and save a bit of load on our releases page (not to mention the added convenience for/. readers).
mozilla.org provies binaries for linux, mac (9 and X) and windows. Other builds (the dozen or so other platforms you're used to seeing at ftp.mozilla.org) are contributed by "platform champions" who take the time to make binaries so that you don't have to.
It's late in the week, christmas and the new year right around the corner. Give folks a little time (usually only a matter of days) to make those builds and send them in to mozilla.org.
Or you could do one better and make a build and contribute it to mozilla.org sooner. See Building a Mozilla distro for tips.
The Labels feature in Mail&News is now fully implemented.
Organize your mail messages with the following new features:
Add labels to messages via context menus or the Message menu.
Clear labels from messages.
Change description and color of the labels via preferences (Edit |
Preferences | Mail & Newsgroups | Labels). Five different labels are
supported.
Add filter rules to set labels to spec.
Mozilla Mail&News now supports basic S/MIME functionality although
the UI is still incomplete.
The Document Inspector is now
enabled in complete installations. The DOM Inspector is a tool that
can be used to inspect and edit
the live DOM of any web document or XUL application. The DOM hierarchy
can be navigated using a two-paned window that allows for a variety of
different views on the document and all nodes within. If you're using
the Mozilla installer, be sure to switch from typical, to
complete or custom install to install the DOM inspector
and JS Debugger.
The Mac OSX toolbar collapse button is now implemented. Press this button
in the title bar to toggle display of toolbars.
The latest and greatest ChatZilla 0.8.5 is now shipping in Mozilla.
Springloaded folders -- Dragging and hovering over a bookmark or message
folder will expand the folder.
Mozilla works again on Mac OS 8.5.
Mozilla now supports
shortcut icons (a.k.a favicons) and custom page icons in bookmarks
and in the personal toolbar.
If you type into the URL bar while a page is loading, your text is no
longer overwritten when the page load completes.
The sidebar now has a Close button.
Print preview is now available on Macintosh.
Mozilla now has support for digest access authentication.
The Save Page operation now also saves images, stylesheets,
objects and applets included in the page.
Mozilla now supports the
longdesc attribute of the img tag.
The longdesc attribute contains a link to a file describing the
image in detail, for those times where the image cannot be downloaded.
To view the longdesc, right click on an image, click 'properties' in
the context menu, then click on the description url in the properties
dialog.
Mozilla has a new advanced preference panel for fine-grained JavaScript
control. For instance, you can disallow pop up and pop-under windows
without turning off JavaScript altogether.
When a page using a strict document type declaration
(e.g. HTML 4.01 Strict) links to
an external style sheet (using <link>, @import, etc)
Mozilla
will only load the style sheet if it is served with a MIME type of
"text/css". Style sheets served with other MIME types, like text/plain,
application/x-pointplus, etc. will not be loaded.
To add the proper css mime type to an Apache web servers, add
"text/css css" to the system mime.types file. Or if you can't do
that, add "AddType text/css.css" to your.htaccess file.
Darn, Slashdot doesn't like title attributes in links:( Repost with good links
So the Mozilla developers are hoping to get more bug-fixing help from the Mozilla and Open Source communities by making it easier for people to write and submit bug-fix patches.
He actually got something right! It's not just developers hoping to get more bug-fixing help though. The Mozilla QA and testing community can use help as well. Gerv (creator of the Patch Maker) is also the maintainer of the Bugzilla Helper which, like the patch maker, was created to make it easier for people to contribute to the Mozilla project. If you're interested in helping to make Mozilla better and you've got DTML skills then you can probably help clean up the Mozilla UI with Gerv's Patch Maker. If you're interested in helping but aren't interested in development there are plenty of other ways to get involved.
So the Mozilla developers are hoping to get more bug-fixing help from the Mozilla and Open Source communities by making it easier for people to write and submit bug-fix patches.
He actually got something right! It's not just developers hoping to get more bug-fixing help though. The Mozilla QA and testing community can use help as well. Gerv (creator of the Patch Maker) is also the maintainer of the Bugzilla Helper which, like the patch maker, was created to make it easier for people to contribute to the Mozilla project. If you're interested in helping to make Mozilla better and you've got DTML skills then you can probably help clean up the Mozilla UI with Gerv's Patch Maker. If you're interested in helping but aren't interested in development there are plenty of other ways to get involved.
They want to see Mozilla running on OS X. That's why they don't care about an Aqua theme for Mozilla.
Mozilla runs well on OS X. It's called Fizzilla and you can get nightly and Milestone testing binaries with the rest of the Mozilla builds at http://ftp.mozilla.org/pub/mozilla/
There are over 100,000 reports in Bugzilla. The Mozilla community has already resolved about 82,000 of those issues. Not all reports in Bugzilla are filed against the Mozilla application suite. We also use Bugzilla for tracking all kinds of other issues from CVS access to bugs in Bugzilla itself.
--Asa
82,000 of 100,000 Bugzilla reports RESOLVED
on
Mozilla's 100,000th Bug
·
· Score: 3, Informative
The recent posting to slashdot about Bugzilla's 100,000th report begs the question, "what other numbers can you give me?" Here are a few of the numbers I pulled out of the database last night. These numbers are all a little rough but should help make the picture a little more clear. About 18.7% of the reports in Bugzilla are still open (UNCONFIRMED, NEW, ASSIGNED, and REOPENED) issues. About 32.8% of the reports have the FIXED Resolution. About 45.4% of the reports in the system are WORKSFORME, INVALID or DUPLICATE. To break that last number down a little more, 26.3% of the database is Resolved as DUPLICATE, 12% WORKSFORME and 7.5% INVALID. About 5.5% of reports in the system are reported against something other than the Mozilla application suite.
So just in case anyone missed it in the fine print, Bugzilla has 100,000+ reports but the Mozilla community has already resolved about 82,000 of those reports. It's probably also useful to know that there are over 32,000 Buzilla user accounts. You can find more on the Mozilla QA and testing community at my O'Reilly OSS Convention presentation (you'll want to use a browser that supports the latest web standards.)
It's your codebase too should you decide to jump in and write some code. If you have performance insightss that you think warrant action please post them to Mozilla's performance newsgroup
In general it is good practice to avoid reading this website if you're interested in accurate reporting about Mozilla or mozilla.org (probably anyhing else for that matter). With articles like "Netscape Denies It Uses Mozilla Code in Netscape 6.1" you have to wonder...
Anyway, if you want real information about what's going on why not ask the folks actually involved. Mitchell Baker (still chief lizard wrangler) had this to say in the mozilla news groups.
Nope. Bugs are being fixed at about the same pace (maybe a little faster). It's just that they are not being Accepted in Bugzilla. So a lot of bugs go from New to Resolved Fixed without having been moved to the Assigned status.
CALL ME CRAZY, but I would think that as a product approaches release, this number should be going DOWN.
That's assuming that all bugs in the product are already known. That's assuming that you treat all bugs as having the same severity. That's asssuming that the number of incoming reports is reflective of new bugs in the projuct. All of these assumptions are wrong.
Slashdot Mirror
Developers fixed a little mroe than 2000 bugs in the 0.9.9 cycle.
--Asa
you cannot select a message without displaying it, thus you cannot forward a spam onto Spamcop without Mozilla starting to render it (and fetching any webbugs in it).
Try collapsing the message area (expanding the threadpane to the bottom of the window). You can do this by dragging the splitter or clicking on the splitter's grippy. When the message area is closed it doesn't load the message.
--Asa
Konqi has been ahead of both Mozilla and IE on it's CSS2 rendering for about 18 months;
. pl ?ID=ETS seems to suggest otherwise and looks to be a little more thorough than your homepage.
I don't know where you get your information but it's clearly wrong. Feel free to state that Konqueror gets you're particular subset of CSS on one particular page you set up but that's a darned small sample from which you make such sweeping statements about CSS support.
http://www.bath.ac.uk/%7Epy8ieh/cgi/listresults
--Asa
This really lessens Mozillas usefulness as a test tool for a web project as you are not guaranteed to see the original source.
And the fact that it's got a JS debugger _with_ JS profiling (ever wonder where your DHTML was spending it's time? Now you can see), it's got a meaningful JS console, it's got the most fully featured DOM inspector (with live DOM analysis) of any free application, it's got the best support for CSS and the DOM of any browser on the planet... None of this matters because you can't conveniently get at original source for some percentage of pages? OK. --Asa
the instant it has smime support in email I'll be there.
You're there! Get 0.9.8
--Asa
The RPMs are daily and milestone build contributions from Chris Blizzard. If DEBs are important to you then make builds and contribute them or find someone that can.
--Asa
Feel free to contribute .deb packages. Got a machine that you can spare to make daily builds?
--Asa
kazaa.com has lame browser sniffing:
//redirect for people with a less than
//version 4 browser
var NS4 = (document.layers);
var IE4 = (document.all);
var ver4 = (NS4 || IE4);
if(!ver4)
location.href= "notsupported.htm";
and hotmail.com works just fine for me on mac, windows and linux mozilla 0.9.7 builds.
--Asa
I think that the last of the known xmouse bugs was recently fixed by dean tessman. Glad it's working for you.
--Asa
steven-ehrbar@home.com said:
See the first line on the release page? It says: "We make binary versions of Mozilla available for testing purposes only!"
netdemonz AT yahoo DOT com said:
That article is old and out of date. Mozilla milestones are meant to be stable releases that can be used as a personal browser.
It is not old and out of date. Mozilla binaries are provided for testing purposes.
--Asa
THE NEWS WE ALL NEED TO HEAR ABOUT MOZILLA IS THAT AOL AND/OR SUN AND/OR IBM AND/OR EARTHLINK AND/OR the EU AND/OR CHINA or ???????
Amen! I'd love to hear that news. Making Mozilla better gets us closer to hearing something like that. There are lots of ways that you can help to make Mozilla better. See getting involved page for some of them.
--Asa
I bet they're releasing the software during the Pacific Ocean timezone to avoid the slashdot effect, cowards).
;-)
I'm sure you said that with a wink, but in case not I'll tell you why we release software late in the evening on Fridays. It's because we bust our butts all week trying to get it wrapped up before the weekend. If we work hard and luck is with us we get it out late in the day Friday. If we run into unexpected problems then it's sometime the following week. Fortune smiled on us this milestone cycle and I think we've got something really good to offer (and on time too
--Asa
> KARMA WHORE!
/. readers).
Um, that's my text. I'm the co-author of the release notes and the originator of the what's new section. I would think that I'm allowed to post that here and save a bit of load on our releases page (not to mention the added convenience for
--Asa
Give it time, friend.
mozilla.org provies binaries for linux, mac (9 and X) and windows. Other builds (the dozen or so other platforms you're used to seeing at ftp.mozilla.org) are contributed by "platform champions" who take the time to make binaries so that you don't have to.
It's late in the week, christmas and the new year right around the corner. Give folks a little time (usually only a matter of days) to make those builds and send them in to mozilla.org.
Or you could do one better and make a build and contribute it to mozilla.org sooner. See Building a Mozilla distro for tips.
--Asa
--Asa
Darn, Slashdot doesn't like title attributes in links :( Repost with good links
So the Mozilla developers are hoping to get more bug-fixing help from the Mozilla and Open Source communities by making it easier for people to write and submit bug-fix patches.
He actually got something right! It's not just developers hoping to get more bug-fixing help though. The Mozilla QA and testing community can use help as well. Gerv (creator of the Patch Maker) is also the maintainer of the Bugzilla Helper which, like the patch maker, was created to make it easier for people to contribute to the Mozilla project. If you're interested in helping to make Mozilla better and you've got DTML skills then you can probably help clean up the Mozilla UI with Gerv's Patch Maker. If you're interested in helping but aren't interested in development there are plenty of other ways to get involved.
--Asa
So the Mozilla developers are hoping to get more bug-fixing help from the Mozilla and Open Source communities by making it easier for people to write and submit bug-fix patches.
He actually got something right! It's not just developers hoping to get more bug-fixing help though. The Mozilla QA and testing community can use help as well. Gerv (creator of the Patch Maker) is also the maintainer of the Bugzilla Helper which, like the patch maker, was created to make it easier for people to contribute to the Mozilla project. If you're interested in helping to make Mozilla better and you've got DTML skills then you can probably help clean up the Mozilla UI with Gerv's Patch Maker. If you're interested in helping but aren't interested in development there are plenty of other ways to get involved.
--Asa
They want to see Mozilla running on OS X. That's why they don't care about an Aqua theme for Mozilla.
Mozilla runs well on OS X. It's called Fizzilla and you can get nightly and Milestone testing binaries with the rest of the Mozilla builds at http://ftp.mozilla.org/pub/mozilla/
--Asa
There are over 100,000 reports in Bugzilla. The Mozilla community has already resolved about 82,000 of those issues. Not all reports in Bugzilla are filed against the Mozilla application suite. We also use Bugzilla for tracking all kinds of other issues from CVS access to bugs in Bugzilla itself.
--Asa
from my report to mozillazine.org:
The recent posting to slashdot about Bugzilla's 100,000th report begs the question, "what other numbers can you give me?" Here are a few of the numbers I pulled out of the database last night. These numbers are all a little rough but should help make the picture a little more clear. About 18.7% of the reports in Bugzilla are still open (UNCONFIRMED, NEW, ASSIGNED, and REOPENED) issues. About 32.8% of the reports have the FIXED Resolution. About 45.4% of the reports in the system are WORKSFORME, INVALID or DUPLICATE. To break that last number down a little more, 26.3% of the database is Resolved as DUPLICATE, 12% WORKSFORME and 7.5% INVALID. About 5.5% of reports in the system are reported against something other than the Mozilla application suite.
So just in case anyone missed it in the fine print, Bugzilla has 100,000+ reports but the Mozilla community has already resolved about 82,000 of those reports. It's probably also useful to know that there are over 32,000 Buzilla user accounts. You can find more on the Mozilla QA and testing community at my O'Reilly OSS Convention presentation (you'll want to use a browser that supports the latest web standards.)
It's your codebase too should you decide to jump in and write some code. If you have performance insightss that you think warrant action please post them to Mozilla's performance newsgroup
--Asa
There are people trying to get work done in Bugzilla and you're making that very difficult. Thanks.
--Asa
In general it is good practice to avoid reading this website if you're interested in accurate reporting about Mozilla or mozilla.org (probably anyhing else for that matter). With articles like "Netscape Denies It Uses Mozilla Code in Netscape 6.1" you have to wonder...
Anyway, if you want real information about what's going on why not ask the folks actually involved. Mitchell Baker (still chief lizard wrangler) had this to say in the mozilla news groups.
Nope. Bugs are being fixed at about the same pace (maybe a little faster). It's just that they are not being Accepted in Bugzilla. So a lot of bugs go from New to Resolved Fixed without having been moved to the Assigned status.
--Asa
CALL ME CRAZY, but I would think that as a product approaches release, this number should be going DOWN.
That's assuming that all bugs in the product are already known. That's assuming that you treat all bugs as having the same severity. That's asssuming that the number of incoming reports is reflective of new bugs in the projuct. All of these assumptions are wrong.
--Asa