Woohoo

I am so happy my website is compatible with most browsers but that W3C validator totally sucks found like 135 Errors and most of them were strange and for example it told me there is no tag called “target” LOL.
:alien: :alien: :alien:

http://gamesorbiter.com

[...] artículo que nos provee de buenas utilidades para conseguir un sitio cross-browser. 0 [...]

Great tools, luckily I passed

[...] cierto, me he dado cuenta de que aún no había comentado sobre esta herramienta mientras leía Is Your Website Cross Browser Compatible (vía [...]

Would really say the majority shouldn’t bother with iE5 and below, they constitute around 1% of the market (http://www.w3schools.com/browsers/browsers_stats.asp), and economically not viable for clients to worry about. Likewise for smaller clients with tight budgets, generally ie6,7 & ff are all that are required (93-96% of total market).

IE4? LOL. As far as I’m concerned, users can expect a degraded experience for anything below IE7. I will not support IE6 any longer. I’m not saying that I don’t test in IE6, and I fix issues which affect the functionality and/or access to the information, but the investment of time spent is not worth the payoff. I say force users to upgrade.

[...] | Sherif Abdou (visto en [...]

@Krasi – you’ve got all kinds of problems with your site, at least for your declared doctype (XHTML 1.1). If you declared HTML 4, you wouldnt see nearly as many errors. And yes, the “target” /attribute/ is no longer valid if your doctype is XHTML. The W3c validator works as it should; you just haven’t coded your site to the specifications of the doctype you have declared.

Also, your hidden input “tafurl” in the “tell your friend” feature is vulnerable to cross-site scripting.

In your article:

“”

should be

“”

Also IE 4 is very very very dead.

great tool! thanx!

Excellent tool.

@ Krasi – there is not tag called target. There is however an attribute called target, but it shouldn’t be used (I’m guessing you were validating in a Strict DOCTYPE to receive that message).

I can’t believe that even 1% of users still have IE 5.5 or below. I would rather spend that time and effort to get things looking right in IE4 – IE5.5 instead on further enhancing the site for better accessibility. Besides, browsers that old can’t handle the more advanced functionality that most clients these days look for (as much as I hate the term, they ask if we do “web 2.0″). Although I agree that you should strive to make a site that’s browser tested and bulletproof, the ratio of time to testing and the lost functionality has to be considered as well.

I've just finished working on my new theme, I checked it with xhtml and css validators, everything is OK, I just needed to see if it was compatible with all browser, that's when I found “Browser Shots” from your post, I'm trying it right now, so thank you for sharing the information

good one

Great posed question, detailed and informed answer; great post, thanks a bunch.

i have a problem
i make a static web site.When i open it in IE7 he open according to tags but whe n i open in Google Chrome or Firefox he get problems.Tags are not on his real place.i want to know how to compatible html tags with other brower that he give same look to all browers.

Yea I gotta agree with you on that one , I dunno what the hell I was thinking approving it lol but didn\\'t wanna hurt anyone\\'s feelings.

To rescue the web designers from this aching job of testing browser compatibility in different browsers there are few websites which offer this service. On these websites you can check the compatibility of your website in all desired browsers. You can find these websites at http://www.bestpsdtohtml.com/7-awesome-resources-to-test-cross-browser-compatibility-of-your-website/

can any help? Browser shots provides similiar visuals on different browsers, yet is different to what the site looks on my end.

Help Please.

Rahul