Analysing Sites

[noteasy]

Hi

I am so frustrated with technology that is not backwards compatible!! We have a number of sites with varying degrees of complexity. Logging on today via IE7 we find that the menu on one of our top sites is not working. It works on every other browser.

Is there a one stop site that analyses code to rate compatibility for all browsers, or a couple at least that you know of, because right now I am experiencing the net as a curse!!!! What do the other developers do?

 

[stix]

http://browsershots.org/

Not 100% accurate but a good first indication.

 

[zagame]

what do the other developers do?

get them all off IE and onto FF


http://freelancefolder.com/7-fresh-and-simple-ways-to-test-cross-browser-compatibility/ - try here for some ideas

http://www.masternewmedia.org/browser-compatibility-testing-guide-the-best-tools-and-services/ - or here

 

[Chelle]

It's a bit of a nightmare making sure that sites are fully cross browser compatible. I use IE tester ( a free download) to test IE in the various versions. It's not perfect, but very helpful.

browsershots.org doesn't provide for browsing the site as IE tester does. Browsrshots just provides screenshots in the various browsers so you can check the look of the site but not the functionality.

 

[guest2013-1]

What do the other developers do?

Test our **** properly

 

[davemc]

Test test test cry a lot and test some more.

 

[guest2013-1]

Test test test cry a lot and test some more.

Amen brutha

 

[GreGorGy]

It is a simple process:
1. get an idea in my head
2. code it
3. smile
4. swear
5. swear more
6. get it working in iCab (webkit) THEN
7. make sure it is happy in FireFox THEN
8. Fire up 'doze and test in IE6
9. swear some more
10. Fix for IE6
11. swear some more
12. Tweak for IE7
13. more swearing
14. Go to 7 above and repeat

 

[guest2013-1]

It is a simple process:
1. get an idea in my head
2. code it
3. smile
4. swear
5. swear more
6. get it working in iCab (webkit) THEN
7. make sure it is happy in FireFox THEN
8. Fire up 'doze and test in IE6
9. swear some more
10. Fix for IE6
11. swear some more
12. Tweak for IE7
13. more swearing
14. Go to 7 above and repeat

and they freak out whenever we spent a few hours "just adding a button"...

 

[SilverNodashi]

It is a simple process:
1. get an idea in my head
2. code it
3. smile
4. swear
5. swear more
6. get it working in iCab (webkit) THEN
7. make sure it is happy in FireFox THEN
8. Fire up 'doze and test in IE6
9. swear some more
10. Fix for IE6
11. swear some more
12. Tweak for IE7
13. more swearing
14. Go to 7 above and repeat

And then we fire-up our old Windows 98 machine, and make sure the website works there as well Oh, and of cause in Linux on Firefox, Opera, Arora and Konqueror.

 

[crazy_cat]

the quirks relating to the various IE versions are well documented. Stick to the stuff that is fully supported across all versions are you will be fine. See here for more http://is.gd/74tVz.

Alternatively(bad idea) use jQuery to help reduce the cross browser CSS issues by setting/updating the css from js.

my guess is that its purely a css issue that can be resolved..

<rant>
its complete BS that you can take say it works on every other browser except ie7=it works on my machine excuse (which is true in some cases).
You doing web dev - know the friggin issues that browsers have:twisted:
</rant>