Slashdot Mirror

Follow this link for a discussion about the upcoming release of a new version of Netscape

Mike Pinkerton, the project lead for Camino, keeps us updated about their progress (among other things) via his blog

The rumoured new version of Netscape being released by AOL will also be based on Mozilla 1.7.

What the article fails to mention however that there appears to be a point of contension between Mozilla developers over whether or not the next long-lived stable branch of Mozilla should be 1.7 or 1.8. Many feel that it is too late in 1.7's development cycle to make it the next stable branch after 1.4. For more information, see here. It's a shame that the Mozilla Foundation apparently feels pressured to make decisions based on time frames instead of quality.

it had to happen sooner or later : mozillazine

also: judging from all the comparisons, test, etc. on FireFox Forums there is absolutely no gain from "optimizing" your binaries. In many cases, using the optimal compiler flags reduces performance.

I can't believe all the bullshit spouted by all the Gentoo turkeys who don't bother doing benchmarks, or even reading the existing benchmark results from those who do.
Compiler optimizations in GCC clearly don't do squat, but changing compilers (like, to ICC) at least has an effect on performance (if you have an Intel processor).
Of course, there's nothing quite like the feeling of spending all weekend compiling a trivial piece of software, and then finding out it has a million and one bugs - kinda like the 2.6 kernel.

mod me troll, pups, but the truth is out.

It makes me wonder if wrestling XHTML and broken CSS implimentations is even worth the trouble.

Does your website have market share in the same regin as Google's? Then by all means, don't bother conforming with the specifications, and I'm sure browser vendors will bend over backwards to make sure that your website will render in their software.

On the other hand, if you don't have that kind of market share, then you can increase your chances of your website rendering correctly by conforming to the specifications.

The plugin was actually released the same day as 0.8.

Almost, but not quite. Someone (Dunderklumpen) on the MozillaZine forums made the suggestion for the extension the day Firefox was released, and I released a barebones extension two days later.

The new news, though, is that the extension finally got a user-friendly interface (no more digging around in about:config) last weekend. The extension has changed a lot over the past six weeks, thanks to the MozillaZine forums users who were interested in its development.

Original idea - Naming extension - anyone?
Extension discussion (obsolete) - Firesomething 1.0.x
Extension discussion (current) - Firesomething 1.1.2

The plugin was actually released the same day as 0.8.

Almost, but not quite. Someone (Dunderklumpen) on the MozillaZine forums made the suggestion for the extension the day Firefox was released, and I released a barebones extension two days later.

The new news, though, is that the extension finally got a user-friendly interface (no more digging around in about:config) last weekend. The extension has changed a lot over the past six weeks, thanks to the MozillaZine forums users who were interested in its development.

Original idea - Naming extension - anyone?
Extension discussion (obsolete) - Firesomething 1.0.x
Extension discussion (current) - Firesomething 1.1.2

The plugin was actually released the same day as 0.8.

Almost, but not quite. Someone (Dunderklumpen) on the MozillaZine forums made the suggestion for the extension the day Firefox was released, and I released a barebones extension two days later.

The new news, though, is that the extension finally got a user-friendly interface (no more digging around in about:config) last weekend. The extension has changed a lot over the past six weeks, thanks to the MozillaZine forums users who were interested in its development.

Original idea - Naming extension - anyone?
Extension discussion (obsolete) - Firesomething 1.0.x
Extension discussion (current) - Firesomething 1.1.2

Bad poster, forgot link to mozilla letter, need more caffeine...

Offtopic: Slashdot requires you to wait 2 minutes between each successful posting of a comment to allow everyone a fair chance at posting a comment. C'mon, /.! Cut some slack for the stupid!

I believe that that may have changed, and that Firefox will remain the brand name of the browser, which - once it reaches version 1.0 - will continue to be available separately to, as well as part of, the suite. That's why so much effort has been expended on the Firefox *image* - the logo, the cute "ads" ("Reclaim the Web", etc) and marketing. Then again, my information dates back at least a few days, so it's possibly out of date already ;)

The original announcement on mozillazine suggests that Firefox is a permanent name, though I couldn't find other postings about the brand-identity. Like I say, this information is probably out-of-date already...

You can also always see the (unofficial) briefing transcripts at Adot's Notblog almost immediately. He does a pretty good job transcribing them as they happen.

--
For news, status, updates, scientific info, images, video, and more, check out:
(AXCH) 2004 Mars Exploration Rovers - News, Status, Technical Info, History.

Dave Hyatt is one of the lead safari developers. He works on webcore. He used to be one of the lead mozilla developers.

He has two weblogs, one for personal stuff, and one for safari stuff. Neither is currently being updated much, but the archive of posts is very interesting.

You can find more current and ex mozilla developers weblogs at mozillazine.

Dave Hyatt is one of the lead safari developers. He works on webcore. He used to be one of the lead mozilla developers.

He has two weblogs, one for personal stuff, and one for safari stuff. Neither is currently being updated much, but the archive of posts is very interesting.

You can find more current and ex mozilla developers weblogs at mozillazine.

Dave Hyatt is one of the lead safari developers. He works on webcore. He used to be one of the lead mozilla developers.

He has two weblogs, one for personal stuff, and one for safari stuff. Neither is currently being updated much, but the archive of posts is very interesting.

You can find more current and ex mozilla developers weblogs at mozillazine.

I'm using the Firefox now, but u should be able to find custom builds for the big zilla in the this forum

This would certainly be cool:

Bugzilla
Mozillazine

Knew I'd seen mention of this recently - I don't follow suite development that closely but this is very interesting and I'm sure there's more info on the associated bugzilla bugs.

Does anybody know why they stopped putting Talkback into the OS X pre-release versions since 1.6 alpha? I thought that was supposed to help them find crashing bugs. Kind of hard to do when you forget to put it in there in the first place.

I can't speak for OS X, but as for Windows, I inquired about the removal of the talkback feature in the nightly builds they had this to say about it:

No, it's not possible to enable it. It's either built into the official builds or its not. Currently the official builds are not being built with talkback because of some talkback server issues, so there is no way to disable it. Hopefully by Firebird 0.9 all of the talkback issues will be sorted, but it's probably not going to happen for the Firebird 0.8 release.

Though if you page down it appears that we shall see it in this release of Mozilla

"The installer releases of Mozilla 1.7 Beta now include Quality Feedback Agent again, allowing users to report crashes, ..."

Hopefully all those new bug reports will help speed up development :-)

I've read your stuff, know of the visual identity team, and thank you for your work (UI is important to me), but are you sure you have the right authority to say these things?

I was under the assumption (from the 03/24/04 minutes) that the --enable-official-branding flag could only be set if you had foundation approval. It seems silly to have the flag that anyone can (and should) use on their builds instead of having it just built in automatically.

Obviously nobodys going to get into a fuss about personal builds. We're talking builds that get distributed in Mozilla's name. Debian can't just use the flag and compile, because they have to be approved to use that artwork.

Alternatively, the contents of this file may be used under the terms of either the GNU General Public License Version 2 or later (the "GPL"), or the GNU Lesser General Public License Version 2.1 or later (the "LGPL"), in which case the provisions of the GPL or the LGPL are applicable instead of those above. If you wish to allow use of your version of this file only under the terms of either the GPL or the LGPL, and not to allow others to use your version of this file under the terms of the MPL, indicate your decision by deleting the provisions above and replace them with the notice and other provisions required by the GPL or the LGPL. If you do not delete the provisions above, a recipient may use your version of this file under the terms of any one of the MPL, the GPL or the LGPL.

It is official; Netcraft confirms: Mozilla is dying

One more crippling bombshell hit the already beleaguered Mozilla community when IDC confirmed that Mozilla market share has dropped yet again, now down to less than a fraction of 1 percent of all web browsers. Coming on the heels of a recent Netcraft survey which plainly states that Mozilla has lost more market share, this news serves to reinforce what we've known all along. Mozilla is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.

You don't need to be a Kreskin to predict Mozilla's future. The hand writing is on the wall: Mozilla faces a bleak future. In fact there won't be any future at all for Mozilla because Mozilla is dying. Things are looking very bad for Mozilla. As many of us are already aware, Mozilla continues to lose market share. Red ink flows like a river of blood.

Netscape 7 is the most endangered of them all, having lost 100% of its core developers. The sudden and unpleasant firing of all 50 Netscape developers by AOL only serves to underscore the point more clearly. There can no longer be any doubt: Mozilla is dying.

Let's keep to the facts and look at the numbers.

Mozilla.org leader Mitchell Baker states that there are 7000 users of Mozilla. How many users of Firebird are there? Let's see. The number of Mozilla versus Firebird posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 Firebird users. Camino posts on Usenet are about half of the volume of Firebird posts. Therefore there are about 700 users of Camino. A recent article put Netscape 7 at about 80 percent of the Mozilla market. Therefore there are (7000+1400+700)*4 = 36400 Netscape 7 users. This is consistent with the number of Netscape 7 usenet posts.

Due to the troubles of Mozilla, abysmal sales and so on, Netscape went out of business and will probably be taken over by AOL who sell another troubled browser. Now AOL is also dead, its corpse turned over to yet another charnel house.

All major surveys show that Mozilla has steadily declined in market share. Mozilla is very sick and its long term survival prospects are very dim. If Mozilla is to survive at all it will be among browser dilettante dabblers. Mozilla continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, Mozilla is dead.

Fact: Mozilla is dying

IF you are into standards and having a uniform webpage in both Mozilla and IE, then you absolutely can't miss Mozie 0.7. It's amazing comparer which supports synchronous websurfing into panels and includes synchronized scrolling... all from the power of an HTA. PS, it's free (hence the plug).

It's in the mozillazine.org news page.

The last two weekly builds have had this turned on. Further information is in this thread.

The bugzilla number for this feature evades me at the moment. I've only used the windows builds provided, but it shouldn't be too difficult to make your own linux build with this stuff turned on.

I've always though of IE as being the 'weak link' BUT check out this post on MozillaZine about how RUS-CERT has critized Mozilla's security policy. Supposedly Mozilla doesn't issue regular patches/update/notices to users - security fixes are only incorperated into the 'latest' release ?!?!!

You have a choice to use another browser, so long as you don't try to access a website created used by Microsoft's products (which can result in minor glitches, to not being able to access links). You can use another operating system, so long as unreliable access to your documents from work is okay with you. You can choose to build and sell computers with another OS on them, so long as you don't think you're going to be able to provide compatibility with legacy applications by dual booting Windows. You can use another product to remotely control your Windows box, so long as -- oh wait, you can't. You can write software to interoperate with Windows for use on another OS, so long as you license your software how Microsoft wants.

It's nice to see that you're such a big defender of your buddy Bill's individual rights. It's a shame he doesn't appear to agree with your philosophies.

I'm currently shopping around for a new provider, though the crazy set of plans and prices that all the firms offer makes it impossible to compare plans or even figure out how much the service will cost.

Wiki's seem to bring together the reasons why the web is seen as useful (disregarding the free pr0n). Easy content creation, accessibility and ease of use. With wiki's you get the added benefit of a central repository to look for the information you need.

As wiki's grow and become known the need for search engines might lessen. The first resort for information will change from google to the relevan wiki. Google will be seen as second in importance. After all, wiki has the structure of yahoo with the benefits of quality content.

Now if only Firefox had the ability to disable animated GIFs. Or has it, and am I missing something?

Yup.

Hmm... did you download a nightly build instead of a more stable build? For me Mozilla was only seriously unstable during the milestone days. But I wouldn't know about what's wrong with Firefox because I use Mozilla Suite on a Win2k desktop (works like a charm). I'd suggest MozillaZine for help. Mozilla bugs in general are classified at Mozilla's Bugzilla site. Both Mozilla suite and K-Meleon are great, although each browser does have their own personalities.

Too bad the logo is non-free and will never be checked into public CVS.

http://forums.mozillazine.org/viewtopic.php?t=5090 7

It is official; Netcraft confirms: Mozilla is dying

One more crippling bombshell hit the already beleaguered Mozilla community when IDC confirmed that Mozilla market share has dropped yet again, now down to less than a fraction of 1 percent of all web browsers. Coming on the heels of a recent Netcraft survey which plainly states that Mozilla has lost more market share, this news serves to reinforce what we've known all along. Mozilla is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.

You don't need to be a Kreskin to predict Mozilla's future. The hand writing is on the wall: Mozilla faces a bleak future. In fact there won't be any future at all for Mozilla because Mozilla is dying. Things are looking very bad for Mozilla. As many of us are already aware, Mozilla continues to lose market share. Red ink flows like a river of blood.

Netscape 7 is the most endangered of them all, having lost 100% of its core developers. The sudden and unpleasant firing of all 50 Netscape developers by AOL only serves to underscore the point more clearly. There can no longer be any doubt: Mozilla is dying.

Let's keep to the facts and look at the numbers.

Mozilla.org leader Mitchell Baker states that there are 7000 users of Mozilla. How many users of Firebird are there? Let's see. The number of Mozilla versus Firebird posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 Firebird users. Camino posts on Usenet are about half of the volume of Firebird posts. Therefore there are about 700 users of Camino. A recent article put Netscape 7 at about 80 percent of the Mozilla market. Therefore there are (7000+1400+700)*4 = 36400 Netscape 7 users. This is consistent with the number of Netscape 7 usenet posts.

Due to the troubles of Mozilla, abysmal sales and so on, Netscape went out of business and will probably be taken over by AOL who sell another troubled browser. Now AOL is also dead, its corpse turned over to yet another charnel house.

All major surveys show that Mozilla has steadily declined in market share. Mozilla is very sick and its long term survival prospects are very dim. If Mozilla is to survive at all it will be among browser dilettante dabblers. Mozilla continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, Mozilla is dead.

Fact: Mozilla is dying

As usual, it's the physical security issues that pose bigger issues than electronic security. At my High School in San Francisco, CA, which is a polling place for all elections, including this one, voting machines are delivered to the school about two weeks before each election, and simply left in a small alcove off of a main hallway. See this for further details on this problem In short, I (or anyone else who enters the unlocked school building) have had many opportunities to simply wheel the entire kit out the door and to bring it back in some time later (this would of course violate state law, so it is left as an exercise to the reader).

Cities need to take basic physical security precautions with their voting equipment as well.

Mozilla's Asa Dotzler may also post a transcript from the press conference later at his blog.

What you need is Firesomething.

(This post brought to you by Yog-Sothoth Earthvulture.)

No, I do not think they should have given up thier name. They are entitled to use it as much as Pontiac is. From my understanding of the situation, the Phoenix code name was changed to Firebird, and then to Firefox for thier final brand. They were code names for projects similar to Merced or Coppermine. The final name was always going to be changed to something once the release came.

Also, from what I remember from the incident I had a very bad impression of the Firebird project. I no longer have any links but what I remember now about it (granted it may be totaly different from what actually happened.. but this is how I view it right now) was the Firebird people attacking Mozilla and writing a very forcefull letter demanding the name change. I believe that a less agressive approach would have produced the same results, and a more positive image for the company.

As far as the relational database vs SQL, I don't know *anything* about the firebird project. All I know is the title here on /. about the 'Firebird relational database.' I always believed the database was relationaly designed and interfaced via SQL but what do I know..

I've already generated a ton of negative comments about my post, but remember this is just my opinion. It's the opinion of a linux sysadmin/perl monk/mysql user who is probably in thier target market. I'm just letting them know why I just don't care.

Some other users have posted some interesting information regarding the 'stink' that the FBDB people did, including mailbombing the mozilla developers. Any project that resorts to that level of action has to do a heck of a lot to not be considered crap in my eyes.

Also, for the record I don't work for/on Mozilla/Firebird/Firefox. I have submitted several bug reports regarding mozilla and I use Mozilla as my primary browser. I have played around with firefox and I do like it. I have never heard of firebird before thier actions, and I have never used thier products ever.

I already suggested the benefits for both Google and mozilla.org for Google to replace their IE Toolbar with an official Google branded Firefox.

Google doesn't want to support a browser they didn't write.

Google could make a version of the Google Toolbar for Firefox. Google could suggest/recommend Firefox without rebranding it, but I'm not sure what they would gain from that.

Some bug fixes that would make Google happier:
* bug 11459, option in Mozilla for mailto: links to go to a webmail service
* bug 62467, highlight all "find" results in the page

You should have brought her Mozilla!

Using "document.all" to infer if the user is using IE or a "standards compliant browser" (by which you mean Mozilla, specifically) is a horribly broken way of doing things.

getElementById() code written for IE generally runs 95% perfectly on Mozilla, in my experience. document.all code would do the same, if given a chance.

My background is working with intranet and vertical market codemonkeys [...] Now, it sounds like you are coming from the HTML guy's perspective

You bring up IE's bugs and malformed DOM and so on, but realistically it's a pretty rare problem

I guess I'm not in any position to say what would break if Mozilla supported document.all, but I can say that tons of stuff would start working.

If you don't like it, don't use it.

"Attention: This is the battle that could cost us the war. If we come together and push all of our might toward a Free Web Browser for Linux, we have a good chance of winning this battle. If we fail, we will lose the war. This is the issue that Microsoft wants us to overlook."

I'm not quite sure how many times I need to explain this, maybe I should stick it in a FAQ or something, but Firefox is not a community driven project. While it gets a lot of benefit from testing, ideas, patches, etc, the prerogative for deciding what will and will not go into the product has always been held by the development group. This is not a new thing, this was in fact the reason this project was created.

Aside from the work that Pierre has done improving Bookmarks and digging around in the toolkit, patches from individual contributors and the infrasturcture (sic) work Brian has been doing on an ongoing basis, Firefox is basically just me at the moment.

Something which you could possibly look at is altering the memory cache, i've just spotted this tip here:

To disable the memory cache completely, add the following code:

// Disable memory cache:
user_pref("browser.cache.memory.enable", false);

Yes, I have the tried the mouse gestures in mozilla. They are not at all consistent. You have to "draw" the gesture exactly with sharp edges or it failes to recongnize

This one might be my ignorance, but I can't get the tabbed browsing to work right on Mozilla. Most of the time it opens new tab for new window but sometimes it will open a new window. Not to mention that the download window always opens a new window

And finally, I love that I can close opera and start it later and have all my open webpages restored. No need to temporary bookmarks. Couldn't find this mozilla.

Also, what we're all discussing now is only a code name for a software being a technology preview, that will likely disappear in the future anyway

The new name is going to be permanent.

From the mozillazine news article on the subject:

The new Firefox moniker is intended to be used as a permanent product name and a strong brand identity will be built around it.

The Theme Site for Firefox

The Extension Site for Firefox

Extensions on Mozdev

Forums for mozilla

Surprizingly the red panda site (Firefox) isn't down yet.

There was quite a good post on Mozillazine about this (sorry, no link, the 'zine seems down right now), where a Moz developer basically said theres a limit to how much warning he can give. If people don't read/don't understand the dire warnings Mozilla give, there's not much Mozilla can do. I'm inclined to agree. It's not just the version number; this statement is still up:

"While this software may work well enough to be relied upon as your primary browser, we make no guarantees of its performance or stability in its pre-1.0 state and it should not be relied upon for mission- critical tasks"

I've also got to suggest that people (AOL users or not) who don't know they're using a browser probably won't download and install a new browser: I think the real problem is fanboys like me encouraging our nearest-and-dearest to migrate to Firebird/Firefox. It's understandable, but not necessarily a good idea.

Incidentally, I've just installed Firefox 0.8 and Thunderbird 0.5 at work. I'm rolling back to Firebird 0.7 and Thunderbird 0.4 tomorrow, and submitting bug reports tonight. Is this a complaint? No - it's what "Technology Previews" are for, to gather feedback from interested users. But it sure ain't something I'd recommend subjecting mom & pop to!

(from Burning Edge)

New features

* Windows installer
* New download manager
* Work Offline
* Add Bookmark dialog: recent-folders dropdown and folder-selection tree (replacing a single dropdown listing all folders)
* DOM Inspector is now included in zip builds
* IDN support
* IPv6 support on Windows 2000/XP/2003

Major improvements

* 220807 - prompt user about invalid text/plain content. (Solves most problems like "Firebird tries to display some .rar files instead of downloading them.")
* 214266 - Find should wrap by default
* 217286 - Cookie whitelist should override session cookie option.
* 142459(?) - Shift+click and middle-click on scroll bar should jump to that location
* 214260 - XPInstall UI improvements
* 33282 - enable external scheme handlers (like aim: and telnet:) in Linux
* 6% faster page loading (comparing December to September on a Tp (pageloader time) graph)

Important bug fixes

* 210910 - Right-clicking a file within a bookmarks folder in the bookmarks menu or toolbar makes that folder inaccessible.
* 203102 - URL typed into address bar lost after switching tabs; "Open in new tab" should prefill URI in address bar.
* 222157 - View Source: Find and Save don't work.
* 213250 - Autoscroll prevents middle clicking on links in XML (XHTML) documents.
* 224416 - Tabs don't remember focused element.
* 216170 - Send Page (as Link) omits query string
* 98564 - caret overlaps the last character in textfield (if positioned after the last char).
* 212366 - Make -moz-opacity apply to descendants as a group, as required by CSS3 opacity
* 219705 - Linux: Blackdown Java crashes, saying "Internal error on browser end".
* 102578 - Linux: Clicking wrongfully fires onmouseout (breaks some dhtml menus, css/edge menus)
* 201209 - GTK2: -moz-opacity makes things invisible.

... and much more!
You can also download a non-installer (.zip) build based on official installer build here and if you look around in the MozillaZine Firefox Builds Forum there's some Windows/Linux Firefox 0.8 builds optimized for AthlonXP/P4/P3/P2/whatever you have.

Be warned that if you use Mozilla Thunderbird on windows that there is a very serious bug! More on in here...

Some spam/virus mails has mangled invalid headers that Mozilla Mail/Thunderbird chokes on. When receiving mails, it simply stops when it encounters the bad mail, but it doesn't mark the previous mails as received or anything. So next time you check mail, you get every mail again until the bad mail, and so on...

A FAQ about the name change can be found here.

There's also a thread on the mozillazine forums about the name change here

Firebird 0.8, hmm?