DISQUS

SherifAbdou - The Design Blog: Is Your Website Cross Browser Compatible ? ; CSS, Html & Compatibility

  • Krasi · 1 year ago
    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
  • Ray · 1 year ago
    The 'minimum' is IE4? I would say that these days, you shouldn't have to worry about supporting anyone using any version that came out before IE6. Sure, accessibility is important, but supporting early browsers just doesn't make sense in a lot of contexts.
  • kluizenaar · 1 year ago
    Come on. IE4/5/5.5 are history. Supporting them is nothing worth anymore. Users that are still on a browser that old have many problems... the layout of a site being the least of them.
  • charles · 1 year ago
    Great tools, luckily I passed
  • Amit · 1 year ago
    Try the following new website for web browser discussion...

    http://www.browserspot.com
  • Rick · 1 year ago
    Real developers run all the popular browsers on all the popular OSes. :ninja:
  • designing.net.nz · 1 year ago
    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_stat...), 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).
  • Allan · 1 year ago
    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.
  • Ryan · 1 year ago
    @designing.net.nz

    Getting browser stats from w3schools is pretty much useless unless you're building a website aimed at web developers and you want to know the browsers they're using.
  • stelt · 1 year ago
    @Krasi: there are different HTML versions, of which some really don't have the "target" attribute.
  • Gilzow · 1 year ago
    @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.
  • Anthony Short · 1 year ago
    @Krasi - If you're being serious, the attribute "target" isn't valid under Strict.
  • Cameron · 1 year ago
    In your article:

    “”

    should be

    “”

    Also IE 4 is very very very dead.
  • Cameron · 1 year ago
    OK :)

    Div

    should be

    div
  • Giacomo · 1 year ago
    great tool! thanx!
  • Rohin · 1 year ago
    Not a problem ! , I believe that supporting older technology will help your international readers who may not have the Latest browsers , then again most people would argue that it only constitutes 1% of the browsers currently active. I guess I'm just more accommodating. :happy:
  • Fubiz · 1 year ago
    Excellent tool.
  • Harry Roberts · 1 year ago
    @ 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).
  • Steve W · 1 year ago
    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.
  • matthew · 1 year ago
    Great tools, luckily I passed :lol:
  • Virtual Millenium · 1 year ago
    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 :)
  • darbez · 10 months ago
    good one
  • David · 9 months ago
    Thanks for referring browsershots, really useful for designers.
  • AlfredN · 8 months ago
    Great posed question, detailed and informed answer; great post, thanks a bunch.
  • wahwa · 8 months ago
    THX