Slashdot Mirror
Mozilla Roadmap Update
wikinerd writes "According to a recent roadmap update for Mozilla, the beta 1.8 version will be unveiled this month, while in the next month a second beta will be prepared. After the Beta2, Gecko engine 1.8 will be finished and it will power Mozilla 1.8, Mozilla Firefox 1.1 and Mozilla Thunderbird 1.1. The developers will then start working on Mozilla 1.9. Here are some nice graphics depicting the roadmap."
Does anyone know what new features will be available in 1.1? I know i know, I could have RTFA..but me too lazy..
"There is no flag large enough to cover the shame of killing innocent people."--Howard Zinn
...that Firefox 1.0 can be improved upon?
Wasn't the Mozilla All-In-One browser supposed to be disbanded and effort placed into Firefox a while back? Are they going to continue delaying and delaying this? I tried to read the article, but it didn't seem to say. I'm curious as to how many people still use Mozilla, anyway.
$lt;br> problem!) but it's a free WYSYWIG HTML editor withoout too many frills or complexities, and it throws out reasonably tidy HTML which can be cleaned up by hand much more easily than (say) Frontpage output.
So what's the future for Composer? I'd love to have it either as a standalone alongside Firefox and Thunderbird, or as an extension to Firefox.
I notice that Thunderbird contains vestiges of Composer (e.g. CSS styles for display modes no longer available)...
I recently started using FireFox at home and am wondering if someone would mind explaning the difference between Mozilla and FireFox. I understand they're both free software projects and are based on the same core technology. Why are there then two browsers? Is it simply a code fork?
The Map
A feeling of having made the same mistake before: Deja Foobar
They should make the gecko do the robot in the about window.
I use Firefox for my Mac, and I have used it for a while now. However, I have found it to use up a godly amount of memory, which sometimes leads to crashes on my mere 512 MB machine. I noticed the 1.0 version was better than the 0.9 version at this, and I hope the 1.1 version is even better.
Anyway, I'm just wondering... does anyone else have these memory problems on their Mac's, or is it just me?
Before anyone evens grabs the oblig. "Yeah but it still can't display Slashdot right!!oneone!1" post, the fix is in the pipeline for 1.1. And it's a race condition with Firefox, not with /.
Slashdot sucks
In order to attract attention from anyone not already familiar with the concept of a software roadmap, you need pretty pictures. Think corporate decision-makers, executives, rich people that want to give Mozilla some money, that sort of thing. Presenting yourself and your product professionally is important, even if it means extra useless charts and diagrams.
End of lesson. You may press the button.
I don't see Sunbird in any of those slides. We still seem to be far away from a complete Outlook replacement that is stable enough to pitch to people. I would think replacing Outlook would be a good investment of resources.
I just want to know if Firefox 1.1 will support rendering Slashdot?
Just an idea, absurd I know, but... since every OTHER site I visit works great with the fox, so maybe somebody should stop posting dupes and fix the HTML?
Yea, too absurd...
- Adam L. Beberg - The Cosm Project - http://www.mithral.com/
Still no SVG?!?!
The only official release of Firefox is 1.0. There are a number of outstanding security flaws in Firefox 1.0 as reported by Secunia and none have been addressed yet. I don't know if there is a nightly release that fixes these flaws, but even if there is, those are not the releases that Mom and Pop download, and it is that type of user that tends to be affected most by security flaws. Doesn't the Firefox/Mozilla team need to release a version 1.0.1 that fixes these flaws sooner rather than later? Unfortunately there is no 1.0.1 on the road map, and version 1.1 is not scheduled to be released until June, if it is on time. By then the oldest unpatched flaw, from August 2004, will be 10 months old! While the severity of current flaws is nowhere near MSIE territory, the age of unpatched flaws will be getting into MSIE territory (well, somewhat, anyway.)
--- What?
Mozilla is using the NEW gecko engine and the article says that 1.8 will be final soon. How is that old? RTFA. Firefox uses mozilla's gecko engine as well.
From mozilla's FAQ:
"Mozilla (Application Suite, also known as SeaMonkey) is a complete suite of web related applications, such as a browser, a mail/news client, a chat client and much more. Firefox is just a browser, which makes it a better choice if you already have a mail client for example. Also, since Firefox is smaller than the whole Mozilla suite, it's faster and easier to use.
Note, though, that Firefox is not the standalone Mozilla browser. The user interface in Firefox differs from Mozilla in many ways. For example, Firefox has customizable toolbars."
So firefox is different than mozilla because...it has a different user interface. Firefox relies on mozilla's work on the gecko engine so to abandon mozilla is to also abandon firefox.
If you wanted to see the actual roadmap itself, starting at this /. article you had to wade through not one, not two, but three intermediate sites to get to it. Thanks a lot for not putting a direct link anywhere in the article, guys.
Have you tried using the suite anytime remotely recently?
The only place it's slower than Thunderbird or Firefox is in startup time. If you turn on the preload feature, then the suite will load faster than the individual apps will. I consider the preload worthwhile, since I've got a browser open the vast majority of the time I'm working on the computer, and if not, I usually at least want the email app open.
If you use multiple individual apps, the suite ends up using less memory as the apps each have their own instance of the Gecko core.
WebCore is open source, but it is written in Objective-C++ (core is C++, interface is Objective-C), which is currently only supported by GCC on OS X (mainly due to the size of the maintainers' egos). Once the main branch of GCC gets Objective-C++ support, it is probable that the GNUstep project will gain a WebCore based browser.
[1] Not in any way an objective measurement, I've just found that a few CSS tags I've wanted to use have been supported by Safari but not by anything else including Gecko.
[2] Again, 100% subjective.
I am TheRaven on Soylent News
About SVG: If you read my article on Mozilla 1.8 Alpha 6 you will see that I mention "Improved support for SVG". So, Mozilla 1.8 already has better SVG support.
Completely different. Safari is built on KHTML, used in konqueror. Which, IME, is a much nicer browser than firefox, at least if you're using kde.
I am trolling
NVU is by Daniel Glazman, and based on Composer.
Much better.
You GOT TO BE KIDDING, right? Almost all people here are using Mozilla as a mail reader and web browser on Linux and Solaris boxes. Now, if they all have to switch to Firefox/Thunderbird THAT would be bloated because Firefox and Thunderbird DON'T SHARE A SINGLE BIT OF MEMORY at runtime (well, they probably share some system libraries but that's not what I mean). They both come with an IDENTICAL Gecko engine but they don't share a single shared library. The result is that memory consumption goes up quite a bit. And also, if I download the source tree for Firefox and Thunderbird I always get the impression that I download the whole Mozilla tree twice and then compile some selected bits and pieces of it (and I still believe that I compile to much and produce some unneeded libs). Why oh why can't they make the promised GRE (Gecko Runtime Environment) which you have to install once and which is shared between all Mozilla products (Firefox, Thunderbird, Sunbird, Nvu and who knows what'll come in the future). THAT would finally convince me to give up the suite. Maybe with Mozilla 3.0 ....
Examples:
The bluetabs template for Mambo CMS:
http://www.mambohut.com/content/view/367/
Slashdot
It will hide results from this search tool, despite showing up fine in IE:
http://windowssecrets.com/winfind/
Anything with ActiveX or VBSCRIPT (not such a bad thing, but people will still complain about it)
Windows Update - A very important site for any Windows user (not firefoxes fault, but this is still a disadvantage to illiterate users)
Sites with the Invision Powerboard have been noted to display threads with lots of posts incorrectly.
Some of these are no big deal, and there are just as many sites that IE displays incorrectly, but it will still be an advantage for IE if firefox displays the same site incorrectly, because people are switching FROM IE, not from firefox.
2. show the url in the location bar for web pages that fail to load
Try this extension.
"...personality goes a long way."
A lot of the new and fixed stuff (including the /. rendering bug) is already available in the nightly builds. I wouldn't install a nightly for Grandma, but they're definitely very usable by anyone of sufficient geekdom:
g htly/latest-trunk/
http://ftp.mozilla.org/pub/mozilla.org/firefox/ni
It's not a matter of whether you or I who are fully capable of finding what we need are able to workaround Firefox not working with Windows Update, it's a matter of whether "Cletus" from the sticks of Mississippi can figure it out.
Why do you think you get the "You must upgrade to IE..." page when you visit Windows Update with FireFox?
If the page wasn't handled correctly, you'd see garbage on the screen. Or an empty screen. Or half of a screen. Basically, you would see the elements that FireFox parsed correctly.
What you're seeing on Windows Update is the result of a script that checks if you're using IE. If you are, it lets you access the main page. If you're not, it tells you to switch to Microsoft's browser. How does FireFox get past this? Clearly, it can't change the script on Microsoft's site. Should it use some fancy algorithm to try and decide which scripts it should ignore and which it should obey? That's opening a whole new can of worms.
It's not an issue of FireFox displaying the page incorrectly. It's an issue of FireFox being blocked at the door.
If you have an example of a page that displays incorrectly without such a limitation on it, then you've got something to discuss.
It also doesn't use the OS X spellchecker in text fields. If it did, I'd never have to use Safari for things like, hmm, this forum post for instance.
Comment of the year
Some of those security issues have been fixed in the nightly builds, but right now the nightlies have a whole whack of regressions that make them pretty close to unusable.
Usually the nightlies are quite usable, but after 1.0 was released they merged in all the Mozilla 1.x changes that had happened in the last 8 months or so, which brought about a whole load of regressions. I expect you'll be able to get more usable nightlies of Firefox 1.1 in a couple weeks leading up to the developer preview. (Also these builds include the perennial Slashdot rendering bug!)
- Allen Pike
Altering time, one time at a time.
I don't think you have a clue what you're talking about. If this is enough for me to claim I'm a developer (or even if it doesn't... I don't really care what trolls think of me).....
r mat=advanced&emailassigned_to1=1&emailtype1=exact& email1=cst%40andrew.cmu.edu&chfieldto=Now
Here's a list of the source directories for Mozilla & Firefox:
accessible browser build caps chrome config content db dbm directory docshell dom editor embedding extensions gc gfx intl ipc jpeg js l10n layout lib mailnews modules netwerk nsprpub other-licenses parser plugin profile rdf security storage sun-java themes toolkit tools uriloader view webshell widget xpcom xpfe xpinstall
Of those, only browser and toolkit are exclusive to Firefox, and most of the code in xpfe is exclusive to Mozilla. Pretty much everything else is shared. There are not different "development teams". Developers working on the core (rendering, networking, the image libraries, etc) are working on both products, since those parts are shared. Other people work on the Firefox frontend mostly, or the Mozilla frontend mostly, or both.
Development is active in both products. It just happens that the Mozilla front end is very mature and stable, so it doesn't change as rapidly. That doesn't mean features aren't being added - I've added a few little things (some of which happen to be in Firefox, some of which aren't), and I'm not the only one working on it.
There are two kinds of fool: one who says, "It is old, and therefore good", and the other, who says "It is new, and therefore better".
Bugzilla blocks referrers from slashdot, so for your copy/paste convenience, the link above is pointing to https://bugzilla.mozilla.org/buglist.cgi?query_fo
My server