Slashdot Mirror
Mozilla 1.1 Alpha Released
theBrownfury writes: "Mozilla.org has released Mozilla 1.1 alpha, the first post 1.0 milestone.
This release has been in the works for almost 2 months now incorporating
over 1700 bug fixes and more than a dozen new features. Including: Quartz
rendering for OS X 10.1.5 users, new layout performance enhancements targeted
at DHTML, faster startup times and more. Here are the release notes and
the link to the releases page
or FTP
for downloads."
getting to that FTP server before it gets slashdotted kinda reminds me of when Indiana Jones is diving under some massive stone door, which is about to shut him in the acient temple.
Tobe honest, I don't see the other problems you mention. When you say "mozilla is often the first app to lose its icons and its interface starts falling to pieces..." -- well this just never happens to me, on NT4 or Linux. Are you trying to use win9x or something? If so, I suggest you nuke that PoS first, install a real operating system (I'd count NT as "real", others may disagree ;) and a pound gets a penny most of your issues will clear up.
The other major cause of issues is installing over a previous version. Try nuking your ~/mozilla (on Windows: %SYSTEMROOT%/profiles/[username]/Application Data/Mozilla ) and reinstalling.
"None are more hopelessly enslaved than those who falsely believe they are free." -- Goethe
Some points you raise:
"* Mozilla is less system tolerant than IE. Mozilla is often the first application to lose its icons and its interface starts falling to pieces. This is probably because of my memory or the CPU overheating.. but IE remains stable until the last minute."
And this is a problem in Mozilla why? You yourself state that it's because of your RAM or your overheating CPU. I don't understand how changing software will fix your hardware problem.
"* Many sites still don't display well in Mozilla. This is the Web developer's fault, but still.. Mozilla can do all of those DHTML menus and stuff, yet I still run into problems on sites that use them. An optional 'IE compliancy' patch in Mozilla would be very very useful!"
This wouldn't help anyone: sticking an IE compliancy patch would only encourage web "developers" to stick to supporting IE specific html. Mozilla renders standard HTML, not "Microsoft HTML". You want more sites to display properly in Mozilla? Email the webmaster and ask him/her to write standard HTML. Once again, you expect the Mozilla team to make such a terrible compromise when you clearly state that "This is the Web developer's fault"
Be kind. There are too many mean people out there already.
I just figured this one out the other day.
To select a portion of the word, drag your cursor so that the next word is highlighted, then back up. IE extends the selection word by word, but retracts it character by character.
"200 Quatloos on the newcomer!" "300 Quatloos against!"
So how many bugs are open on IE? How do you know it's 10x as many bugs? For that matter, how do you actually raise a bug on IE if you find one? Microsoft do their best to hide that kind of information.
The fact is Internet Explorer is closed source. You have no idea how many bugs are open on it, how many are fixed between builds, the quality of patches, the quality of the code or even what features are being worked on at any given time. Mozilla allows you to do all which consequently means a lot of people are motivated to find and reports bugs and often submit patches.
Besides, a lot of the so-called bugs on mozilla are covering feature work, more deal with embedding and API cleanup, more are dupes, more are issues restricted to specific sites and more deal with issues on specific platforms. They might all be labelled "bugs" but the number of crash/non-functional/quirk issues are actually a subset.
I took a couple of screenshots of Slashdot rendered with and without the Quartz rendering of Mozilla 1.1A.
Wow. What a difference.
http://www2.canisius.edu/~graciem/mozilla.html
--saint
If you are using a proxy like junkbusters then This will solve your problem:
10.3. I'm using a transparent proxy (such as Junkbuster) and I'm having weird browsing problems. What's happening?
Some transparent proxies (including some versions of Junkbuster) do not handle HTTP/1.1 properly. The first thing to try is to go to Edit | Preferences | Advanced | HTTP Networking and select 'Use HTTP 1.0'.
UNIX/Linux Consulting
The branch will have a subset of the fixes that land on the trunk. It will not have all of the new features that the trunk has, although some of the features will eventually migrate to the branch after they are well tested on the trunk.
Mozilla builds a set of technologies from which end user products can be built. We provide these technologies to everyone but our primary consumers are companies and organizations that use our technologies in their products. The stable 1.0 branch and the 1.0.x releases on that branch are intended for companies and organizations looking for the most stable technologies they can get. The 1.x development trunk is intended for testing large changes and new features as well as working toward a Mozilla 2.0. We intend to have stable points on the 1.x trunk about once a quarter for those vendors who are a little less conservative or need the latest and greatest feature set for use in their products.
So to answer your question, yes, we will have two different development paths but one will be tracking the other as closely as stability will allow. You won't _have_ to choose from anything but if you're interested in helping us test our latest technologies then please grab trunk (1.x) builds and report any problems. If we need help testing builds on the more conservative 1.0 branch then we'll let you know.
--asa