Mozilla 1.5 Alpha Available
An anonymous reader writes "Mozilla.org released Mozilla v1.5 alpha today, with flavors available for Linux,
Mac OS X, and Windows. Some of the new features include Composer enhancements, Chatzilla logging, multiple tab window closing confirmation, and quicksearch support in about:config. A more detailed rough changelog is also available. In a somewhat related note, Mozilla 1.4 has been downloaded over a half million times in the past 3 weeks (not counting mirrors)."
Those guys actually list about 500 issues they've taken care of with this release. Go people go! .zip file "as...," Moz appends a .x after the .zip extension
some useful ones imho
*Mozilla crashes when magnifier is used
*Browser crashes when javascript closes a window [@nsDocShell::InternalLoad]
*Save As > withoua> extention result is a html fila> and a directory > *When saving a
*mozilla can't subscribe to existing imap folders
*Browser crashes on HTTPS urls - Trunk M140RC1 [@cert_get_next_general_name
*Loading personal certificates
*pop3 password failed error msg missing
Mike Pinkerton as well as others continue to work on Camino. It is by no means dead, but nightlies are highly variable in quality.
That said, the bug button in Safari still exists (it is disabled by default in 1.0) so report those bugs so it can get even better! This will help KHTML advance more quickly as well!
Read the updated roadmap, they're not going to make it for 1.5 it seems. Considering that Mozilla recently gained its independance, and a good portion of fulltime gecko developers have been let go, I think they're due for a milestone or two of of getting their bearings and realigning around the *birds.
.... give them a month or two to straighten things out, it'll be worth it.
Besides, IE7 comes with longhorn, Mozilla has plenty of time, and is already in the lead, Firebird and Thunderbird are already proving to be ready for prime time
I always set
" , true);e .close", true);e .directo ries", true);e .locatio n", true);e .menubar ", true);e .minimiz able", true);e .persona lbar", true);e .resizab le", true);e .scrollb ars", true);e .status" , true);e .titleba r", true);e .toolbar ", true);g e", true);w ", true)
user_pref("dom.disable_window_flip", true);
user_pref("dom.disable_window_move_resize
user_pref("dom.disable_window_open_featur
user_pref("dom.disable_window_open_featur
user_pref("dom.disable_window_open_featur
user_pref("dom.disable_window_open_featur
user_pref("dom.disable_window_open_featur
user_pref("dom.disable_window_open_featur
user_pref("dom.disable_window_open_featur
user_pref("dom.disable_window_open_featur
user_pref("dom.disable_window_open_featur
user_pref("dom.disable_window_open_featur
user_pref("dom.disable_window_open_featur
user_pref("dom.disable_window_status_chan
user_pref("browser.block.target_new_windo
to keep crappy web pages from disabling my menus.
Great! But Mozilla isn't complete until you've got MOUSE GESTURES. Honestly, I've found that mouse gestures coupled with tabbed browsing is such a more pleasant experience than anything that Microsoft is peddling. It seems that the best innovation is still coming from elsewhere and Microsoft is playing catch-up. Didn't I hear about IE having tabbed browsing in the next release?
I hate liberals. If you are a liberal, do not reply.
I was thinking the same thing. Apparently that was the plan but they have been forced to change things (perhaps due to the Netscape break).
Buried deep in the To Do list on the official Roadmap page is one small but significant change. This is the passage that has been added. (There are probably other changes today as well but that is the one I noticed and pertains to this question).
It's clear now that we will not be able to switch to Mozilla Firebird by the Mozilla 1.5 final milestone. Instead, we expect Mozilla 1.5 to coincide with Mozilla Firebird 0.7. But we intend to implement the new application architecture in the next several milestones, till most of the community is won over to the new apps.
Hmmm... At the bottom of the page, the Roadmap states that it was last changed July 22, 2003 - so it appears that they were forced to make the change and only sort of let it be known. Wonder what is going on?
Well, until then, I will keep using Firebird. But for those migrating - another positive is that 1.5alpha is 1.4 Mbs smaller.
Funny.
It hasn't been five minutes since I posted this comment and I've already figured out what the problem is.
In order to set up the language support, you must go to View -> Character Coding -> Customize..., and add the language support you want for browser rendering. This is *not* at all what the popup message indicates, and seems like something that needs to be present in Preferences as well, and more clearly labelled. If a person is likely to be using a web browser in more than one language, then they'll probably want to configure all the language options all at once, so there's no sense in putting them in two separate places in the application.
So, kudos to Moz for a lightweight multi-language browser, but demerits for making it counter-intuitive to configure.
"Mod, mod, mod...and another troll bites the dust."
A bit of explaination: the "timebomb" preference is a relic from the Netscape days. It provides a countdown until some final date, which when reached, the application will provide an expiration notice popup and request that the application stop working.
Unfortunately it may take a bit longer than that. It'll take a year to get something shippable to end users (brendan)
This is disappointing to me as I use Firebird regularly and am really impressed, but I guess they (the developers) know what they are talking about.
It's not really supported or production worthy, but try typing "chrome://messenger/contents/messenger.xul" and "chrome://chatzilla/contents/chatzilla.xul" into your URLbar.
It's clearly not totally debugged, and weird stuff can happen (who knows), but it seems to sort of work for me.
That quote from staff minutes was out of context. I was citing the agreement I'd reached with all-volunteer Mozilla Firebird developers before the Mozilla Foundation was announced, where 0.7 would coincide with 1.5, 0.8 with 1.6, etc. I went on to say to staff, at that meeting, that if we get more time from the developers, the schedule could be shortened.
Now, we hope to hire a Firebird developer fulltime at the Mozilla Foundation, and we expect to go faster. No promises yet; the roadmap will be updated in due course.
I've been seeing a lot of firebird checkins lately (past 3 weeks or so).
The shareholder is always right.
About
;-) I recommend you take a look at http://cascades.mozdev.org/ or build yourself the editor in mozilla/extensions/editor/cascades.
: yes, I can agree with that. We currently use a lot of
because Gecko forces us to do so. If there is no content, there is no frame (basically, that's how we call the abstract boxes rendered on the canvas); and if there is no frame, we can't place a caret... Given how much the layout team was axed last week, I don't think we'll have a fix for this very big issue any time soon. I am myself working on another approach, ie make Composer get rid of any useless
as soon as possible. You have to understand that's not a simple task _at all_. I currently have a fix in my own tree, but it's not fully satisfactory yet.
About definition lists: I agree too and I am working on it.
About nested lists, bug 54479: that's a major issue, and solving it is a HUGE work. I have a partial fix for this that helps **creating** valid nested lists but does not handle copy/paste yet.
About editing stylesheets, you were probably on another planet during the last year and a half
Daniel Glazman, Mozilla Composer module owner and author of CaScadeS.
Lots of tips & tricks for mozilla at MozillaTips logically enough.
They've got some good stuff already, but could probably use the extra traffic !
D.
--- These are not words: wierd, genious, rediculous