What browser do you use?
Moderator: General Moderators
What browser do you use?
I dont know if this topic has been dealt with, so sorry if Im spamming.
I would like to know what the best browsers would be to test my webpages on.
At the moment I have IE, fx and Opera on my machine. Is this efficient, or are there other browsers that I'm missing?
thanks a lot guys
I would like to know what the best browsers would be to test my webpages on.
At the moment I have IE, fx and Opera on my machine. Is this efficient, or are there other browsers that I'm missing?
thanks a lot guys
- aaronhall
- DevNet Resident
- Posts: 1040
- Joined: Tue Aug 13, 2002 5:10 pm
- Location: Back in Phoenix, missing the microbrews
- Contact:
That covers most of them, though they may render differently on different operating systems, and across different versions. Fonts are another thing to worry about. The only major one you're missing is Safari for Mac. If, for some reason, you don't have $4,000 to drop on a mac to test your website, have a look at http://browsershots.org/.
- Chris Corbyn
- Breakbeat Nuttzer
- Posts: 13098
- Joined: Wed Mar 24, 2004 7:57 am
- Location: Melbourne, Australia
I use Firefox at work, Safari at home (although some things about it are starting to bug me).
The major ones though:
IE >= 6
Firefox >= 1.5
Opera >= 8
Safari (no idea on versions)
Other free ones:
Camino (Mac)
Konqueror (Linux/KDE)
Epiphany (Linux/Gnome)
Lynx (Linux/Console)
AOL (barf!!)
Netscape (Pretty much unused these days)
The major ones though:
IE >= 6
Firefox >= 1.5
Opera >= 8
Safari (no idea on versions)
Other free ones:
Camino (Mac)
Konqueror (Linux/KDE)
Epiphany (Linux/Gnome)
Lynx (Linux/Console)
AOL (barf!!)
Netscape (Pretty much unused these days)
- Kieran Huggins
- DevNet Master
- Posts: 3635
- Joined: Wed Dec 06, 2006 4:14 pm
- Location: Toronto, Canada
- Contact:
Camino and Netscape use the same layout engine as Mozilla (the Gecko engine) - their results should be identical.
Konqueror and Safari both use the khtml engine - maybe you could install Linux (in a VM?) and test for Safari (via Konqueror) that way? I don't see why it wouldn't be the same...
My general rule of thumb is to design to web standards and test in IE 6, FF, and (finally) Safari.
Konqueror and Safari both use the khtml engine - maybe you could install Linux (in a VM?) and test for Safari (via Konqueror) that way? I don't see why it wouldn't be the same...
My general rule of thumb is to design to web standards and test in IE 6, FF, and (finally) Safari.
- seodevhead
- Forum Regular
- Posts: 705
- Joined: Sat Oct 08, 2005 8:18 pm
- Location: Windermere, FL
Best way to test when designing is to use Firefox as your primary development test browser (very standards compliant), and then use IE6 beside it as you go along to make sure any IE bugs are worked out... most notably the double-margin float bug.
I don't see a need to test in IE5.5 or earlier. There just isn't anyone really using those old browsers anymore. You'd be wasting too much time debugging for less than 1% of your viewership.
I don't see a need to test in IE5.5 or earlier. There just isn't anyone really using those old browsers anymore. You'd be wasting too much time debugging for less than 1% of your viewership.
- seodevhead
- Forum Regular
- Posts: 705
- Joined: Sat Oct 08, 2005 8:18 pm
- Location: Windermere, FL
I would STRONGLY suggest NEVER using IE as your primary development/testing browser. The goal with CSS is to test it in the most standards-compliant client you can get your hands on. Because your ultimate goal is to write standards-compliant CSS. Thus, write compliant code, test in Firefox, make any necessary adjustments. Then after Firefox is where you want it, THEN move on to IE and others. Make the proper adjustments for the not-so compliant browsers, and so on. I cannot stress this enough.
alvinphp, seodevhead is correct in this. Starting with IE will get you in trouble. Or at least will cost you a lot of development time. Because you start coding for a buggy browser. So in fact you write your CSS wrong. Then, when you see that standards-compliant browser display your site differently, you waist your time writing hacks for your buggy code. Leading to more buggyness and hackyness, etc etc.
My experience lately is that if you write clean, standards-based code for FF, you hardly need any more work to get things correct in IE. Well ok, the occasional quirk comes forward now and then. But using conditional comments and feeding IE a rule or two separately usually does the job.
One tip I would have is to keep the most obvious IE bugs in the back of your mind while writing your code. That might seem to contradict my previous point, but what I mean is that when you already know something is going to cause trouble in IE, deal with that immediately. As an example: the box model. Don't blindly give every box you have both paddings, widths and borders. Give the box a width and no padding and just give the content of the box a margin.
So for me it's now:
- Firefox mac
- Safari mac
- IE (5,6,7) windows
- other browsers (Opera, etc)
My experience lately is that if you write clean, standards-based code for FF, you hardly need any more work to get things correct in IE. Well ok, the occasional quirk comes forward now and then. But using conditional comments and feeding IE a rule or two separately usually does the job.
One tip I would have is to keep the most obvious IE bugs in the back of your mind while writing your code. That might seem to contradict my previous point, but what I mean is that when you already know something is going to cause trouble in IE, deal with that immediately. As an example: the box model. Don't blindly give every box you have both paddings, widths and borders. Give the box a width and no padding and just give the content of the box a margin.
So for me it's now:
- Firefox mac
- Safari mac
- IE (5,6,7) windows
- other browsers (Opera, etc)
- Kieran Huggins
- DevNet Master
- Posts: 3635
- Joined: Wed Dec 06, 2006 4:14 pm
- Location: Toronto, Canada
- Contact:
a "whitespace reset" will likely save you some pain as well - at the top of every page's CSS I include:
this will help bring IE and FF in line, as they have different default styles for these elements.
Code: Select all
/* whitespace reset */
* { padding:0; margin:0; }
h1, h2, h3, h4, h5, h6, p, pre, blockquote, label, ul, ol, dl, fieldset, address { margin:1em 5%; }
li, dd { margin-left:5%; }
fieldset { padding: .5em; }
/* /whitespace reset */The goal of CSS is not to test it in the most standards-compliant client, if that was true then you would not start with FF first.seodevhead wrote:The goal with CSS is to test it in the most standards-compliant client you can get your hands on. Because your ultimate goal is to write standards-compliant CSS first.
If you start with IE then you take care of the CSS problems (using hacks) up front. Having started with IE first to build a page I can say from personal experience that I do not lose a lot of development time by starting with IE.matthijs wrote:Or at least will cost you a lot of development time. Because you start coding for a buggy browser. So in fact you write your CSS wrong. Then, when you see that standards-compliant browser display your site differently, you waist your time writing hacks for your buggy code. Leading to more buggyness and hackyness, etc etc.
Thinking about this more I am realizing it does not matter which browser you start with as you still have to make it work for all the browsers you consider important.
I don't agree. And I think it's a strange way of developing. Why would you start writing code for a browser which doesn't follow the specifications? Then by definition your code ends up written wrong. To give a simple example. You layout a few boxes. Width 200px, padding 20px, border 10px. Now in IE5 that box takes up 200px. So you can fit in 4 of them in the parent box of 800px. Great.alvinphp wrote:If you start with IE then you take care of the CSS problems (using hacks) up front. Having started with IE first to build a page I can say from personal experience that I do not lose a lot of development time by starting with IE.
Now you open up FF. Oops. Boxes don't fit!
Would you care to explain this? Why don't you want to test in the most standards-compliant browser? And why is FF not standards-compliant?alvinphp wrote:The goal of CSS is not to test it in the most standards-compliant client, if that was true then you would not start with FF first.