Hi everyone,

 

I have read that it is best to design a site for FireFox first, and then make it work in other browsers first, as all the quirks are well documented (quirksmode.org for example).

 

Is this right? Does FF most closely match the "standard(s)".

 

Cheers,

 

Martin

I always design for FF first, then check in IE7 and IE8, then all the rest.

Hello i design in firefox check it in ie 6 and 7 on my pc's then use broweser shots for other browsers i do not have

I personally tend to design for chrome, but i never have any issues in Firefox either, My only reason being is that some sites have slightly mis-alignments with chrome, so i can prevent these, and that chrome scored higher on the acid test.

 

The only problem is, sometimes having firebug is a must, in which case i'll be using FF too at the same time. I recommend you download opera too, it seems to always have some odd quirks with me and inherited widths.

 

This is a great way to test browsers though http://www.xenocode.com/browsers/ (requires a small plugin though).

Thanks guys!

I design for Firefox and use hacks/fixes for IE. I don't normally have problems with Opera or Safari but if I do, the forum is always willing to help out :-)

I design for IE first for the simple reason that 80% of all web users surf using one of the versions of IE, target and satisfy the largest market first.

Don't you then have the problem of trying to make fixes for Firefox etc?

I design for FireFox first and then make hacks for IE. Its a real pain when you run into a web-kit problem for Chrome and Safari as these are standards browsers and really making a javascript solution to detect web-kit browsers and display different styles is not the way to do things.

When I design a page, I constantly preview my work in chrome and firefox. Only one I am happy with the result, do I check things out in IE 8, 7, 6. The reason for using chrome is that for some reason it is quicker than ff when loading pages off a local server. My general approach though is to keep things simple and correct from the beginning. I try ensure that my code validates from the offset and fix problems as they creep in rather than waiting for the end before validating the code and attempting to fix all the errors. I also try to keep my coding as simple as possible, generally using relative positioning for primary divs (not absolute) and making use of inner-wrappers for padding as this solves the IE6 quirk of doubling up padding on floated divs. The result is most of the templates I have made in the last couple of months have worked pretty well in all browsers. Another thing I keep in mind and check out, is what the site will look like when images are disabled and or css. While it is difficult to make a site look pretty under these circumstances, I try to ensure the site is still functional.

Don't you then have the problem of trying to make fixes for Firefox etc?

 

 

In my opinion its easier to get a site working in IE first then make some minor fixes for firefox, safari, chrome etc etc when ever i have attempted to do it the other way around and design for firefox first I always find its major hassle to get it up and running properly in IE,

 

And to be honest if things are not quite right in safari, chrome, opera, I tend not to worry to much as the user base for these browsers is pretty small compared to IE.

 

(just to clarify, when I say "not quite right" I mean minor differences in rendering, not totally broken, or vastly different in appearance.)

Firefox is the best browser for designing as it matches the compatibility of the designs and gives a very attractive look to the design

i usualy design for firefox first because i have firebug installed and it helps a lot in the process of coding the site. after the design is complete i check with IE6 and IE7 and after that with safari, opera and chrome. in the end the site is displayed perfect in all the browsers.

I'd go for FF first

 

<a href="http://www.webdesignedge.net" target="_blank" title="Web Design Edge, Low Cost, Overseas Website,Development Alternative,web design,advanced solutions, search engine optimization,search engine service,thailand webdesign, web marketing,web development,e-commerce,web service, multimedia, click cart pro,web programmer, Web design blog,thailand webdesign,"><img src="http://www.webdesignedge.net/images/banner/88x31.jpg" alt="Web Design Edge, Low Cost, Overseas Website, Web design blog" width="88" height="31" border="0" title="Web Design Edge, Low Cost, Overseas Website,Development Alternative,web design,advanced solutions, search engine optimization,search engine service,thailand webdesign, web marketing,web development,thai seo,thailand seo,SEO,google ranking,web application, ecommerce,e-commerce,web service, multimedia, click cart pro,web programmer, Web design blog,thailand webdesign, web marketing,web development"/></a>

Wow, that was a bit of a fail.

 

Thanks again for the replies. It seems that FF and Chrome are the most "standards" based browsers to design for (if you are set on having a completely compliant site).

 

I can see where you're coming from T_break designing for IE first. I'm just not convinced that the target market I'm aiming at will be all IE based. Also, I have mild OCD, and one of the ways this manifests itself is wanting perfect code and total standards compliance

 

(I'm not joking on that last point by the way... It really does unsettle me! )

 

Cheers,

 

Martin

I think FF is simply the best browser that is why we are targeting it.

I also agree with the standard FF is using.