Mozilla 1.1 Alpha Released 464
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."
Wooo! (Score:3, Interesting)
Re:Wooo! (Score:2)
> dhtml... takes forever to load those
There's a bug with large background images slowing page rendering; I haven't checked for a few weeks, it may be fixed now. Otherwise, perhaps it takes a long time because it's, like, a big file? Have you tried saving it off locally and reloading? (clear the cache if you want to be really anal about it ;)
Java Problems... (Score:2, Insightful)
Re:Java Problems... (Score:4, Informative)
Even then, lots of applets are MS pseudo-java (and only work in the Microsoft VM) rather than real Sun/IBM/etc. Java. AFAIK the games.yahoo.com used the MS-Java specific crap (for no good reason) last time I checked.
Applets actually written for Java 1.3/1.4 work brilliantly, I find, and the fact that 1.4 applets get the DOM of the page they are embedded in is cool, too. Next step: drag-n-drop applets in Composer
Re:Java Problems... (Score:2, Informative)
I had a lot of trouble installing java on moz 0.9.8 a while ago, but when I did a full reinstall with 1.0 it went without a hitch, installed, and runs absolutely perfectly...
Re:Java Problems... (Score:2, Insightful)
Make sure you have the Java plugin installed!
Re:Java Problems... (Score:2)
did you follow the steps to get java correctly installed? I followed both proceedures on the mozilla site to get java working well and both make the java-intense yahoo.com games to play pretty much flawlessly.
Re:Java Problems... (Score:2)
Re:Java Problems...Solution (Score:2, Informative)
Here's the solution: cd over /usr/local/mozilla-1.0/, remove all Java-related files and the java2 directory. Then go to java.sun.com and reinstall.
Everything now seems to work fine. Don't ask me why it works, though.
Re:Java Problems... (Score:2, Insightful)
Re:Java Problems... (Score:2)
I've forced IE to use the Sun JDK and plugins and it didn't have any problems using applets, while Mozilla (0.9 something, 1.0 wasn't out at the time) choked on several of them. Hell, it couldn't even find parts of the Sun plugin.
For some reason... (Score:5, Funny)
Re:For some reason... (Score:4, Funny)
Re:For some reason... (Score:2)
Re:For some reason... (Score:2)
Re:For some reason... (Score:2)
It isn't like Netscape 6 is snappier than Netscape 4, now is it? But Mozilla sure seems to be.
Well done to the team (again) but.. (Score:2, Informative)
However, there are several things that stop me from using it 100% of the time. I still stick to IE for about 25% of sites, because.. of all the little bugs! I'm hoping some have been cleared up in this Alpha. They include:
* Keyboard not responding sometimes when you open a new Mozilla window (this is in Bugzilla)
* When you click on some links, it doesn't go to the destination.. and it just displays a picture off of the current page! Hit Refresh and you finally go on your way.
* 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.
* Mozilla often bawks if you're loading large JPEGs into it direct from hard disk.. and it just displays a blank/white screen with scrollbars.
* 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!
Re:Well done to the team (again) but.. (Score:3, Informative)
* In the Windows browser, selecting text will even do strange things like go back the the previous page, or close the browser window! It may be the gestures getting confused, but it's highly annoying.
Re:Well done to the team (again) but.. (Score:2, Insightful)
huh?, this is one of the main complaints I have about IE, stoping a selection mid-word is almost impossible using it. Mozilla handles it much more gracefully.
Set your gestures to the middle mouse button and never worry about it again, it's simple really.
Re:Well done to the team (again) but.. (Score:5, Informative)
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.
Re:Well done to the team (again) but.. (Score:2)
Re:Well done to the team (again) but.. (Score:2)
Re:Well done to the team (again) but.. (Score:2)
Re:Well done to the team (again) but.. (Score:2)
This seemingly random behavior is due to the mouse gestures being mapped to the left mouse button by default. You can change which button you use to use mouse gestures in the preferences panel.
-inq
Re:Well done to the team (again) but.. (Score:5, Informative)
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.
Re:why mozilla still sucks (Score:2)
Did you try 1.0? 1.1 is clearly marked as an alpha release, it's supposed to have kinks. I've had no problems with 1.0 on Linux or Windows 2000. I miss the download manager, but that's about it. I'm looking forward to the 1.0.x releases for greater stability on MacOS 10 so I can get my mac friends using it.
Re:why mozilla still sucks (Score:3, Informative)
The mozilla 1.0 stable branch will continue as 1.0.x, and the 1.x series will continue as test milestones for evaluation of the latest features added to the trunk development. Each release cycle will be about 13 weeks long, consisting of 5 weeks work then an ALPHA release, another 5 weeks then a BETA release, then a week or so freeze before the milestone.
This release is 1.1 ALPHA. Lots of nice things in there for those who are following Moz and don't mind the shortcomings, but if you just want to complain, stick to IE.
Re:Well done to the team (again) but.. (Score:2)
Re:Well done to the team (again) but.. (Score:5, Insightful)
"* 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"
Re:Well done to the team (again) but.. (Score:2)
You want more sites to display properly in Mozilla? Email the webmaster and ask him/her to write standard HTML.
While I agree with you, I'd like to defend the original poster by saying that this isn't always an option. Especially not when dealing with corporate web pages, even those of small companies.
Many web designers charge more, sometimes much more, to produce standards-compliant web pages without all their Javascript and IE-specific tricks. And a lot of companies, especially small ones, will fight tooth and nail against anything that makes their web page less flashy or "attractive" to users.
(The biggest irritation here for me is the thousand-and-one nonstandard ways of using drop-down navigation menus. To say nothing about the horrible usability of said menus in the first place!)
Re:Well done to the team (again) but.. (Score:3, Informative)
* Not supporting my (home) wheel mouse. Telling users they need new drivers is not an option!
* Losing an entire folder of bookmarks being dragged. The bookmark section in general needs a fair amount of work
Despite that, the pop-under tabbed browsing is the best thing since er the wheel mouse. I just want 'em both!
Re:Well done to the team (again) but.. (Score:2, Informative)
How many times have people had to go to a hardware company's support site to get the latest drivers for their hardware? Or even the latest version of ActiveX to support the new game they want to install? In windows this has been a fact of life for years and this is not a mozilla only problem. At least you have an option of getting a new driver, most hardware companies are completely oblivious to anything but windows.
I've been using mozilla for almost 2 years. I've never had a problem with the wheel mouse. I've installed it on both linux & windows machines. And I've used several brands of wheel mice including the genius net mouse which is'nt even a wheel but a toggle switch really. And they all worked perfectly. You need to give alot more information.
Re:Well done to the team (again) but.. (Score:2)
IE compatibility patch... (Score:4, Insightful)
This brings up one of my older thoughts: you know how we can format sites with user-defined stylesheets, how about user-defined
Re:Well done to the team (again) but.. (Score:5, Informative)
If you are using a proxy like junkbusters then This [mozilla.org] 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'.
Virtual hosts on servers (Score:2)
Re:Well done to the team (again) but.. (Score:2)
Um, no. It would be a Bad Idea to perpetuate IE crap.
Re:Well done to the team (again) but.. (Score:2)
- Quartz integration? Looks the same a 1.0 did. Ok, they used the standard file dialog but I think they have a lot left to do in this department. Not that I'm complaining... I like it. I just expected more from a release that gets Quartz Integration in the Release notes.
- Download Manacore? I'm sure the download manager is cool and all, but when I download something it doesn't use it... and when I try to open it, mozilla politely goes away leaving me a core.
I shouldn't complain too much though. Mozilla 1.0 was great and this is just an alpha... Keep up the good work.
Re:Well done to the team (again) but.. (Score:3, Informative)
Admittedly I needed a bit of hackery to set the font in the UI, because by default the UI font uses a non-antialiased font (it picks up the GTK setting and there's no GUI to change that). But you can even override that easily by putting the following in a file called userChrome.css in your profile directory:
dialog, window, menu, menuitem {font-family: sans-serif !important}
That last remaining issue will go away when the port to GTK2 is completed because GTK2 will allow an antialiased font to be the default. Alternatively, you *might* be able to pick a truetype font as your default GTK font and have it work now, but I haven't tried that so I'm not sure.
Stuart.
Re:Well done to the team (again) but.. (Score:2)
Of course, if you're on Linux.. not quite such a great font manager just yet
Although.. I'm sure I see antialiased fonts on my notebook in Mozilla.. (running Gnome 1.2, Enlightenment, under RedHat 7.0)
Quartz rendering. (Score:2)
Woo-hoo! I wonder if this is using that Silk [unsanity.com] program I haven't gotten around to installing yet.
Doesn't matter. Mozilla was the only thing I was going to install it for, because decent looking text is the only thing I miss from OmniWeb.
--saint
Re:Quartz rendering. (Score:2)
Hallelujah! (Score:4, Interesting)
Next step is to figure out an easy way to automate transferring my contacts from Outlook (I've got an iPaq with all my contacts which syncs to Outlook) to LDAP, then both Mozillas (and my webmail program for externally accessing email) can use the same contacts list.
Zilla (Score:2, Funny)
Kazilla was released today, in version 0.000241. Although there is nothing noteworthy about this release of Kazilla, the popular P2P application, please be aware that it includes Spyzilla and Spamzilla software that may or may not install Screwmezilla based upon your approval, acceptance or non not acceptance of the EULA attached to Kazilla.
The ever anticipated front-end to Slashdot's popular moderation system was also released to the public. Modzilla 0.7,28.90 is a GUI interface that streamlines and integrates popular random client-side interactions with www.slashdot.org's acclaimed moderation system.
Stuff (Score:2)
But anyway, I am no longer scared of demonstrating Mozilla to friends and colleges. Crank on Mozilla! You've come a LONG way since I first tried you out (Mozilla M5).
Re:Stuff (Score:5, Funny)
I think you *do* need that spell-checker yourself.
Re: Spellchecker (Score:3, Informative)
latest build... (Score:2, Informative)
ftp://ftp.mozilla.org/pub/mozilla/nightly/late
Download manager (Score:3, Insightful)
About time too. This feature should be a core piece of any Browser. I should be able to schedule downloads, do segmented downloads and autmatcially resume downloads right from within the browser, not have to use some thirdparty app that is not integrated.
/b
Re:Download manager (Score:5, Interesting)
Multithread/segmented download is based on the assumption that the other people downloading are using one download process. And by using more your self, you get more bandwidth which you steal away from the other people. This is a extremely anti-social stance.
Also, it is a bitch for sysadmins. If everyone used multi-process downloads, suddenly your site has to keep in mind that those 50 people downloading all use 5 processes, so you have to cater to 250 download processes (which eats mem, slows your machine down, and is generaly unfair for people who do play nice!)
What i have done on all my FTP servers, is to put this line in the
throughput
The 20000 is the max download speed (set to 0 for unlimited), but the 0.2 is the interesting part. It means that every extra download processes for the same client only gets a factor 0.2 of the download speed! This way if someone is anti-social enough to download using 5 threads, his download is actualy _slower_ then when he would use a single process. Thus keeping the bandwidth available for the people who play fair.
Downloading of different sites? (Score:5, Interesting)
Even taking away the segmented download features I think the browser should still have some of the other features of Gozilla/Getright/etc.
/b
Re:Download manager (Score:2)
Re:Download manager (Score:2, Informative)
DoS in Mozilla/X (Score:4, Interesting)
when X/XFS is running?
(For those of you who don't know, you can kill X
by including "body { font-size: 1666666px; }" in a stylesheet
Re:DoS in Mozilla/X (Score:4, Insightful)
Re:DoS in Mozilla/X (Score:2, Informative)
Re:DoS in Mozilla/X (Score:2)
X crashing because I entered an obvious bogus value in a gimp dialog is one thing. X crashing because I clicked a hyperlink in mozilla is a very different thing.
that doesn't mean the underlying bug in X should not be fixed - it should. however, mozilla should still check stuff before handing it to the local system.
disclaimer: I wrote the bugtraq posting. the above is why I labeled it a DoS in mozilla.
Re:DoS in Mozilla/X (Score:3, Funny)
See, this is why I'm keeping with ext2.
New release very soon after 1.0 (Score:3, Interesting)
If someone there is worried about people facing this 1.1 new release when, in press releases they have been told about 1.0, then don't worry. The big milestone of 1.0 is about compatibility: the interfaces have been frozen so further development will be easy to do. This is a concert only for enterprises developing applications based on Mozilla technology (PDAs, portable aps, embedded devices), not for the desktop end user.
Text comparison. (Score:5, Interesting)
Wow. What a difference.
http://www2.canisius.edu/~graciem/mozilla.html
--saint
Re:Text comparison. (Score:2)
Re:Text comparison. (Score:3, Interesting)
Re:Text comparison. (Score:2)
Re:Text comparison. (Score:2)
Seems okay to me now, but I'm on my work machine with a Studio Display LCD - the original Moz rendering was jagged because the display is so crisp.
I've got a CRT on my system at home - it'll be interesting to see what it looks like there.
--saint
Re:Text comparison. (Score:2)
Re:Text comparison. (Score:2)
Thanks for the heads-up. It's fixed now.
(Hey, it worked in Moz. How was I supposed to know?
--saint
GTK2 port of Unix versions? (Score:4, Interesting)
Does anyone know if they're planning to replace GTK 1.2 with GTK 2.0 soon as default toolkit on Unix platforms? By default I mean it uses GTK 2.0 if found without having to use --with-toolkit=gtk2 configure option of whatever it's called. I think basic GTK 2.0 support has been in since February or so and I personally tested it sometime in April or May (had to get some patches somewhere and apply to source from CVS, wasn't yet committed back then) and it worked fine on my mainstream system (i686 PC running Debian/unstable). Also some days ago I grabbed some snapshot debs from an APT repository announced on galeon-devel mailing list. Packages included Mozilla with GTK2 support and Galeon compiled from source from the HEAD branch of their CVS. That GNOME 2.0 version of Galeon is already almost quite usable, very cool.
Anyway, IMHO, it would be appropriate to begin public testing of new rendering back-end in early stages of 1.1 alphas by compiling official snapshots for Unices with GTK 2.0 support enabled. Any words regarding the issue?
Xlib (Score:3, Interesting)
People who prefer Gtk over XUL should probably use Galeon [sourceforge.net] instead of Mozilla.
Where is Mac OSX version? (Score:2)
Eric
Where is the source? (Score:2)
Features Mozilla really needs (Score:2, Interesting)
I'd love to see a way to allow/block particular plugins for certain websites, as we can now with cookies. A way to globally turn all plugins on/off easily would be useful as well.
OT... the start up speed from 1.0 to 1.1a is significantly faster on my machine, and 1.0 was fast enough for me!
Quartz Rendering for i686? (Score:2)
Not to mention that I can't get the screen resolution below max (16KX12K) on my laptop. I've run Xconfigurator a dozen times and tried the CTRL-ALT-Minus trick but it won't change.
Poor mozilla font rendering in Red Hat 7.3 (Score:4, Informative)
Actually, I found that the biggest problem with Mozilla in RedHat 7.3 was that I had installed the AbiWord word processor when I installed the system. AbiWord happens to have some really poor quality fonts named according to the Microsoft convention.. Arial, etc. So any web page that gives you something like
<font face="Arial, Helvetica, sans-serif">
will cause Mozilla on X to go and find the lousy AbiWord fonts, no matter what you try and do in the Mozilla font preferences.
The solution is to comment out the reference to the AbiSuite fonts in /etc/X11/fs/config from finding the AbiWord MS-named fonts.
Mozilla on RedHat 7.3 was totally unusable until I did this.
Too bad it doesn't run on UFS (Score:4, Insightful)
Really sucks, because when I got rid of OS 9 on my tiBook, I reformatted it all UFS, thinking I'd never have need for HFS+ again. Oops...
At least Chimera doesn't have that problem (although there are a slew of others...)
Re:1700!? (Score:2, Interesting)
If you look at the about screen for the Konqueror browser they have about 25-30 programmers each doing a little job on their own. Thats why it really rocks!
Mozilla however was hacked together by thousands of serperate programmers each adding salt.
Maybe it would be better if mozilla was developed like the linux kernel was, and thats the main programmers reveiwing patches before they are accepted.
Re:1700!? (Score:2, Informative)
To a large degree a myth. Yes, there are many people who add small patches but a substantial portion of the core code is written by paid Netscape employees. The really hairy parts tend to get hacked on less because there is such a steep learning curve. The idea that it is a chaotic free for all is entirely bogus.
Maybe it would be better if mozilla was developed like the linux kernel was, and thats the main programmers reveiwing patches before they are accepted.
Doh. Every patch requires at least [mozilla.org] two reviews.
Re:1700!? (Score:2)
In addition to this, new features are added all the time, and bugs in these new features will be reported and consequently fixed.
I don't think you have quite considered the amount of work which must go into a web browser.
The system you are working on doesn't sound very impressive compared to a full-featured browser. The system specialized and works in a carefully adapted environment, doesn't it? You can't even begin to compare your simple little system to a full-featured web browser which must handle today's standards as well as correct others' errors.
This has got nothing to do with open-source, but with the kind of project being worked on.
Then again, I guess it is possible that IHBT... In fact, it is quite likely. I don't know why I even bothered replying...
Re:1700!? (Score:2)
This is a different kind of project with the existance of some very capable products (functionality-wise) already in the market but a goal of better quality. The end result though is a product that will also reach a much wider range of users than our trading and clearing systems do.
roadmap: Re:This is a milestone (Score:2, Informative)
1.1alpha 12-Jun-2002
1.1beta 17-Jul-2002
1.1 09-Aug-2002
Security fixes in mozilla 1.0 not included here.
Re:roadmap: Re:This is a milestone (Score:2)
If you look at the roadmap [mozilla.org] we can see that 1.0, 1.01, 1.02 etc are on a different branch than 1.1alpha, 1.1beta, 1.1 and 1.2alpha. Does this mean that each branch will have progressively different bug fixes and feature sets? Will we eventually have to choose from two different mozillas? Or am I simply reading it wrong?
What's up with this?
Re:roadmap: Re:This is a milestone (Score:2)
Does this mean that each branch will have progressively different bug fixes and feature sets?
Yes. The 1.0.x series of releases will contain bug fixes, but no new features. The 1.1, 1.2, etc., series of releases will contain both bug fixes and new features. In addition, there may be some bug fixes made to the 1.1, 1.2, etc., releases that are not made to the 1.0.1, 1.0.2, etc., releases, because the risk of fixing the bug is too high (that is, fixing a particular bug might cause multiple other bugs to appear).
Will we eventually have to choose from two different mozillas?
Yes, in the sense that you can decide either to install the 1.0.1, 1.0.2, etc., releases, or you can decide to install the 1.1, 1.2, etc., releases. However I expect most Mozilla users to install 1.1, 1.2, etc. The 1.0.1, 1.0.2, etc., releases are for people who don't care about the new features but instead want a stable version that doesn't change much from release to release; for example, a company building a Mozilla-based product may be interested in this.
Re:roadmap: Re:This is a milestone (Score:2)
I wonder if the developers working on the 1.0.x releases will get bored quickly?
Re:roadmap: Re:This is a milestone (Score:4, Interesting)
They are the same developers that are working on the 1.x releases. Why would they get bored checking in a fix to the trunk and to the branch?
--Asa
Re:roadmap: Re:This is a milestone (Score:2)
Does this mean that each branch will have progressively different bug fixes and feature sets?
Yes. The 1.0.x series of releases will contain bug fixes, but no new features. The 1.1, 1.2, etc., series of releases will contain both bug fixes and new features. In addition, there may be some bug fixes made to the 1.1, 1.2, etc., releases that are not made to the 1.0.1, 1.0.2, etc., releases, because the risk of fixing the bug is too high (that is, fixing a particular bug might cause multiple other bugs to appear).
Will we eventually have to choose from two different mozillas?
Yes, in the sense that you can decide either to install the 1.0.1, 1.0.2, etc., releases, or you can decide to install the 1.1, 1.2, etc., releases. However I expect most Mozilla users to install 1.1, 1.2, etc. The 1.0.1, 1.0.2, etc., releases are for people who don't care about the new features but instead want a stable version that doesn't change much from release to release; for example, a company building a Mozilla-based product may be interested in this.
Re:roadmap: Re:This is a milestone (Score:2)
That all depends what bug fixes there will be in 1.01. I bet most develops will keep using the bleeding edge 1.1 trunk and only real bugs and security fixes will make it on 1.0.x The 1.0 manifesto [mozilla.org] states that 1.0.x is mainly for stabilty of the API and a reference implementation. This may not be the best version.
The maintarget for 1.0 is for vendors to have a reference implementation.
Like linux.: There is a and 2.2 and 2.4 kernel version. They all are maintainted. From 2.2 you know it is stable, but you are not sure it works with the latest hardware. from 2.4 you know It is fast but you do not know if your old applications work on it. for 2.5 you know it has the most features, but you are unsure if it is stable. In the end you let ret-hat or suse choose for you like you let netscape (or
Re:roadmap: Re:This is a milestone (Score:2)
1.0 was the API freeze release. Browsers in the 1.0.x series will be guaranteed to have an API which is feature- and bug-copmatible with the original 1.0 release. This means that developers can target 1.0 and not have to worry about the API changing every release in the "stable" branch.
1.x (past x=0) is the branch for continuing development. The API can and will change in these releases.
The point of the branching is that developers can target 1.0 and be confident that their applications won't be breaking on the very next release. Also, the developers can continue hacking at the code like they like to do, and the bugfixes that don't break the API can be backported to the 1.0.x branch. Best of both worlds scenario, really.
-inq
Re:roadmap: Re:This is a milestone (Score:5, Interesting)
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
Re:excuse me but (Score:2, Informative)
I benchmarked it against IE on one of my p0rn sites, it loaded the page in under a second, IE took over 4, every time.
Re:excuse me but (Score:2)
Interesting ... at home on my blazing slow 28.8* I have found that it is neither faster or slow than non-pipelined browsing when using multiple pages at once. Are you using a broadband connection?
*[no rants please about upgrading my connection, there is nothing better available, not even 56K, where I live]
Re:excuse me but (Score:2, Informative)
In that case your connection will just about always be saturated, and you'll get no benefit from `pipelining', which works by downloading several files at a time. It's only useful if you usually have some unused bandwidth.
Re:excuse me but (Score:4, Insightful)
This has the greatest effect on high latency connections, not low bandwidth ones (though, of course, the two often go hand-in-hand), so that a 28.8 modem to a website hosted by your ISP probably won't show much difference, but a cable modem to a creaking, cruddy server on the other end of the planet will.
Re:excuse me but (Score:2)
AFAIK, http pipelining is a function of HTTP 1.1, and I didn't/don't think that a lot of people or places are actually serving up HTTP 1.1 data.... much less is are any of those groups enabling pipelining, because it is implemented incorrectly, to varying degrees, across so many httpd server packages.
I'd be interested if anyone could verify or correct what I've said... but seems that my last bit of research regarding http pipelining said something to that effect.
Re:excuse me but (Score:4, Insightful)
No, it wasn't. It was released on the 11th. There has been a freeze for a while, builds might have been calling themselves 1.1a, but the official release build was on the 11th.
See here [mozillazine.org] or here [mozilla.org] for the history.
Re:excuse me but (Score:2, Informative)
Just so people know: Not all http-servers support pipelining properly. While these semi-broken servers wont crash Mozilla you may sometimes notice http-headers spilling on to the screen. See bugzilla entry #144574.
Re:excuse me but (Score:3, Informative)
--Asa
Re:excuse me but (Score:3, Interesting)
Re:1700 bugs?!?!?! (Score:5, Informative)
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.
Re:1700 bugs?!?!?! (Score:2)
Re:crapzilla???!!!??? (Score:2)
Re:Whatever happened to FullScreen in Linux? (Score:2)
Have you tried Mouse Gestures [mozdev.org] yet? Latest versions include gestures to go to full screen & back again. True, it's not a pretty button, but, hey, you get what you pay for.