views:

83

answers:

4

I am on the stage where I need to make my website cross-browser compatible. I need tips on how to get started.

I have developed my website on firefox, so it works great with firefox.

I guess I have to download a couple of versions of all major browsers now, right? Then just test each browser one by one?

Should I do this before uploading the entire website onto a server or afterwards?

All tips and SW which makes this easier is appreciated.

BTW, it is a classifieds website using MySql, Solr, PHP, js etc...

Thanks

+2  A: 

Cross-browser compatibility is best planned for in advance, as there are ways to build your site that will make it much easier.

  • Consider using a CSS reset script like Eric Meyer's.
  • Consider using a JavaScript library like jQuery.
  • You can make use of Adobe BrowserLab to do cross-browser testing.
  • Consider the mobile audience.
RedFilter
Whats the css reset script for?
Camran
It makes it easier to write a proper site to begin with, although it doesn't help to test it.
Thom Smith
The reason for a CSS reset is that all browsers have presentation defaults, but browsers don't necessarily have the *same* defaults. See http://meyerweb.com/eric/thoughts/2007/04/18/reset-reasoning/
RedFilter
I thought CSS reset was a great idea years ago, but now I'm starting to think it's too heavy handed, not to mention with so many browsers being more up to date, not as necessary. I fully agree with using jQuery, it's the safest way to be mass browser compatible, as well as having the fastest JS possible, it's a total win-win library.
TravisO
Is adobe BrowserLab FULLY reliable, or do I need to make tests with actual browsers also?
Camran
@Camran: BrowserLab is just a first-level sanity check. if you have a logged-in state, it will be of little help.
RedFilter
A: 

You need to have some kind of local webserver so you can edit the code and test it in a comfortable way. It is also helpful if you make it accessible for validator.w3.org so you can do syntax checking.

Testing it in IE6, 7 and 8, Firefox and Chrome would be a good start I would say.

Johan
There's no need to use the online W3C validator when the "HTML Validator" plugin for Firefox exists, no public URL needed.
TravisO
A: 

Since you are working with server side code, you need to have a server.

Once the site goes live you will need both a live and a development server.

David Dorward
I have a development server... If wampserver counts as one!
Camran
It does, although the fewer differences there are between the development server and live server, the better. I try to keep a VM configured identically to the production server for testing.
David Dorward
A: 

Yes, I'd make it cross browser compatible before uploading to the server. The reason for this is that you may need to change the server-side code, adding ids and classes to the markup, plus it may well be necessary to change the markup. Make sure it's working locally first.

IE Tester is very useful for testing on the various IE browsers. I'd ensure that I've tested it on a Webkit browser (such as Chrome), a Gecko Browser (such as Firefox) and Opera. See this list for different browsers.

darasd