Hi ,
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
+4
A:
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
2010-10-06 12:12:52
I did see something like this but it was a paid thing! And I thought my only option was virtual pc!!
giddy
2010-10-06 12:27:46
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
2010-10-06 13:06:58
A:
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
2010-10-06 12:20:17
+4
A:
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
2010-10-06 12:20:43
A:
You can take a look at this list too http://www.quirksmode.org/css/contents.html . Hope this helps
Jeff Norman
2010-10-06 12:20:53
+3
A:
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).
haylem
2010-10-06 12:56:12