Browser Compatibility, IE, FireFox, Standards

One of the biggest challenges to web developers is accomodating the browser. Standards with the DOM and CSS have come a long way, and so has the implementation. (Before you start harping about "Internet Exploder vs. Firefart", do yourself a favor and review the over 200 behavior and other changes they baked in as of IE 7 RC1, which was released today, at the IE7 blog page and see for yourself).

So now that you have an RC for IE which basically means no more code changes until the next release, it's time for developers to start zeroing in on the defects and anomalies and workarounds for rendering, positioning and behaviors between different browsers.

I for one would appreciate some sort of a site that highlights the differences between say IE, Firefox and Opera, one-by-one according to type (CSS, DOM, script, etc) with workaround examples for each. A community site wiki - style, with some developer participation, would go a long way toward helping the community as a whole and cut down on the incessant flame - throwing from one camp to the other (which is currently reminiscent of the Middle East).

Comments

  1. Peter-Paul Koch's quirksmode.org [ http://www.quirksmode.org/ ], has some great content on browser incompatibilities & differences. You can look under the W3C DOM ( -> W3C DOM Compatibility tables ) menu from the main page or elsewhere ( http://www.quirksmode.org/bugreports/index.html , http://www.quirksmode.org/css/quirksmode.html ) on the site.

    ReplyDelete
  2. Thanks, Anil. I have seen this but I didn't realize the site went into such detail on this particular subject.

    ReplyDelete

Post a Comment

Popular posts from this blog

Some observations on Script Callbacks, "AJAX", "ATLAS" "AHAB" and where it's all going.

IE7 - Vista: "Internet Explorer has stopped Working"

FIREFOX / IE Word-Wrap, Word-Break, TABLES FIX

System.Web.Caching.Cache, HttpRuntime.Cache, and IIS Recycles

FIX: Requested Registry Access is not allowed (Visual Studio 2008)