<p>The MSIE team aren’t that particularly concerned with protecting legacy browsers, as around 40% of the IE users use browsers that Microsoft itself consider legacy. Of the other 60% (versions 7 and up), they do at least release regular updates that the users have no control over. But sure, let’s maintain that most of the FF users do not build their own nightlies, IE does have a slight advantage over FF in terms of security, although the Chromium group releases more regular updates (no need to rebuild) for Chrome than IE does.</p>
<p>
</p>
<p>This I have to dispute. The FF rendering engine have long been seen (albeit without much complaint) as the slowest rendering engine in the web design community. Do a simple rendering benchmark test and you’ll see why. But then again, we designers tend to view Firefox as the liberator that finally brought the internet into a place of sunshine…</p>
<p>As for the rest, there are currently three browsers on the market that actually passes all three of the ACID rendering tests, and the three of them together consists of less than 10% of the market share of the browsers. Of these, Chrome and Safari both promises to support future standards. Firefox have also pledged to do so, although its development is bit slower compared to the other browsers. </p>
<p>The MSIE team on the other hand, recently announced that they will not support all of the CSS2 specifications and none of the CSS3 specifications, they will also only partially support HTML5 specifications (not to mention a lack of true XML mimetype support for even the current specs).</p>
<p>So for me, as long as you don’t choose IE, I’m fine with whichever browser you use.</p>
<p>Assign the blame where it is due: If only chrome were supported by commonapp</p>
<p>It’s not that hard to make a website operable in all major browsers. The CommonApp is just in a position where they can do what they want, and students can’t really complain.</p>
<p>EDIT: CHROME IS THE BEST. Originally I had firefox, then, right after I posted that it was, it crashed…so screw it, it’s no longer number one lol.</p>
<p>I used to be a Firefox-only person, but for some reason it works really slowly on my new laptop. So I switched to Chrome a few months ago and I’m surprisingly happy with it. [:</p>
<p>Failboat: FF Slowest web browser?..exaggeration by the web designing community much? </p>
<p>I personally think it’s the fastest. I brought it up with my brother and he said it’s between FF and Chrome. Haven’t used Chrome as much as firefox or as he had but i have for sometime and Firefox seems to beat it for the most part.</p>
<p>I haven’t used Chrome since several years ago when it first came out (I don’t remember if I used a beta or the first stable version), but Opera is FAR faster and much less of a resource hog than FireFox. I remember finding Chrome’s interface weird. I haven’t used IE since IE 5 I think. And Safari is for Macs, right?</p>
<ol>
<li><p>Chrome–fastest, has amazing features. I love how it simplified the space into three convenient lines and its cool Tab Management features.</p></li>
<li><p>Firefox & Safari. Both are great in their own ways (I’ve tested both).</p></li>
<li><p>Everything else.</p></li>
</ol>
<p>I used to be a firefox devotee until Chrome got adblock recently. It isn’t as good as the adblock for firefox, but is sufficient. I find that I save milliseconds when navigating websites and clicking on links when using Chrome.</p>
<p>Safari is a bloated, buggy piece of crap. I hate all apple software made for Windows, with their sketchy user agreements and poor performance.</p>
<p>Chrome is definitely my favorite. Very fast and good for multiple tabs. I have the others as well, and Mozilla doesn’t even work (it won’t even open to the home page), IE is IE, Safari is a pain, and Opera is actually pretty good except for its not that great for Facebook games.</p>
<p>Hehe, by a mere 4% (96% compliancy with the latest stable build), but there’s a branch within the dev that will build a fully ACID3 compliant instance. The problem with it however is that it must revert to a semi-legacy rendering method for everything, therefore making the browser extremely slow (at least it was when I built it nearly a year ago).</p>
<p>" Hehe, by a mere 4% (96% compliancy with the latest stable build), but there’s a branch within the dev that will build a fully ACID3 compliant instance. The problem with it however is that it must revert to a semi-legacy rendering method for everything, therefore making the browser extremely slow (at least it was when I built it nearly a year ago). "</p>
<p>Well, as said before, firefox being fully complaint only means it will be better for web design. Although not used mainly for that, it would be cool to be able to follow elemnst (well), Javascripts and DOM.</p>
<p>And going back to the semi-legacy rendering is a certainly not going to happen. lol</p>
<p>and to your last statement (at least it was…): impressive.</p>
<p>opera > ff > chrome >>>>>> ie on my computer
opera works the best when the computer hardware is not as sophisticated (2.8ghz single core p4, 1gig of ddr1 ram…)</p>