2

Is there any way I can find out if CSS I am using works fine with most of the browsers ? I got some reference http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html

TopCoder
  • 4,206
  • 19
  • 52
  • 64
  • 4
    Nothing beats manual, human, visual testing. – Pekka Oct 06 '10 at 12:12
  • What we do is read the HTML header to detect the browser, then use Javascript to render the correct stylesheet for the browser. We started doing this less often since switching to JQuery-UI. – Koekiebox Oct 06 '10 at 12:26
  • If you are using Safari or Opera, they have renderers for other browsers built-in. – Koekiebox Oct 06 '10 at 12:27

5 Answers5

4

You can simply test it in most of the browsers, if you so wish. Things like http://browsershots.org or Expression Web SuperPreview can be of great help there.

Joey
  • 344,408
  • 85
  • 689
  • 683
  • I did see something like this but it was a paid thing! And I thought my only option was virtual pc!! – gideon Oct 06 '10 at 12:27
  • Browsershots does have a paid option. The free option is painfully slow. Also, of course, it only helps for static content; it won't help at all for any dynamic content. – Spudley Oct 06 '10 at 13:06
4

Obviously the best way to find out if your code works in all browsers is to actually run it in all browsers. But I acknowledge it's not always as simple as that! (especially trying to work out exactly what's happened when you do get problems)

My CSS compatibility Bible are the Quirksmode.org compatibility tables.

The author of that site has written a very comprehensive set of tables showing virtually every feature of CSS along with its browser compatibility, including notes about bugs and other odd quirks.

I simply can't recommend it highly enough.

Spudley
  • 166,037
  • 39
  • 233
  • 307
4

Some pointers to good tools or research data, in recommended processing order.

Clean It

While you're there, you might as well start from a clean slate:

Validate It

Not always possible in the real world with gory hacks, but still. Good baseline to avoid screw-ups.

Unit-Test It

Not all of them are exactly unit testing tools, but the idea is too checked that the computed style are actually what you expect and that elements are where you expect them to be after styling.

User-Test It

Use full-user or semi-user-automated checkers (they run, you check):

Compress It

Once it's cleaned and good, you may want to compress it (and redo the steps above with the compressed version):

Research It (and Re-Do It)

Research similar questions and tools (until, well, the end of days, and add to this list).

Community
  • 1
  • 1
haylem
  • 22,460
  • 3
  • 67
  • 96
0

I've been pretty happy with adobe browser lab https://browserlab.adobe.com/en-us/index.html but browsershots is always my first choice

alekone
  • 127
  • 3
  • 11
0

You can take a look at this list too http://www.quirksmode.org/css/contents.html . Hope this helps

Jeff Norman
  • 1,014
  • 5
  • 25
  • 42