And then the Spiders Came
Developers were learning an important lesson: separating concerns. Sites were now to have HTML as their structure and CSS as their layout. Behavior was still an issue but new libraries such as script.aculo.us and the now ubiquitous jQuery were coming around the corner.
CSS Selectors Everywhere
jQuery was a godsend to this new breed of Web Developers who had just learned CSS.
.error div and you wanted that
.error div to fade out, you used the same CSS selector.
Progressive Enhancement & Graceful Degradation
Practicing What You Preach
In early 2013, jQuery 2.0 is set to be released and drop support for older Internet Explorer (oldIE) browsers.
Whilst jQuery has allowed people to add interactivity unobtrusively, it hasn’t guaranteed that developers have built their sites in a way that has included non-jQuery workflows. These developers could be in for a shock if they drop 2.0 into their existing projects expecting oldIE to continue working.
In general, if you’ve coded your website in the right way, when users visit your site in an old browser, although the user interface may not be as snazzy, the user’s experience will be that they can get to the information they want or perform the task they came to your site to do.
A Moment of Reflection
Whilst the jQuery team are releasing an oldIE compatible 1.9 shortly before 2.0, the advanced announcement of jQuery 2.0 has given us all a reminder of why we fell in love with jQuery in the first place and why it’s important to progressively enhance our sites to allow them to gracefully degrade in certain environments.
I’d love to hear your comments on what you think of the announcement that jQuery 2.0 is dropping support for oldIE and any special plans (if any) you’re making as a result.