InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

JQuery 1.7 Brings HTML5 To IE6-8, Gets Deprecation Policy

Posted by Roopesh Shenoy on Nov 14, 2011

Sections
Development
Topics
jQuery ,
Releases ,
Javascript ,
Release ,
Web Development ,
Dynamic Languages ,
Version Control ,
Languages ,
Source Control ,
Programming

JQuery 1.7 has recently been released, with improvements such as new Event APIs, Better performance of Delegated Events, HTML5 support for IE6-8, support for AMD spec and more. The team has also started deprecating certain features in an effort to keep JQuery slim.

Following are some of the new and interesting features in JQuery 1.7 -

  • New Unified Event APIs – .on() and .off() replace .bind(), .delegate(), .live() and .unbind(), .undelegate(), .die() respectively
  • Improved Performance on Delegated Events for most common cases
  • Better support for HTML5 tags in IE6-8 such as <section> with methods like .html(). Older IE versions still require html5shiv or Modernizer
  • Toggling animations such as .slideToggle() or .fadeToggle() work more intuitively – stacked animations get reset properly when previous animation is terminated prematurely
  • Support for AMD Specification – JQuery now co-operates with AMD-compliant script loaders such as RequireJS or curl.js

The JQuery team has also announced that they will start deprecating out-dated features to help make the code base leaner and also improve performance. Some APIs like .live() and .end() have been deprecated in JQuery 1.7 – they will continue to work, but their use is not recommended for compatibility with future versions.

Some non-standard features have been completely removed in 1.7 -

  • event.layerX or event.layerY
  • jQuery.isNaN() (undocumented utility function)
  • jQuery.event.proxy() (undocumented method)

You can read more about the new deprecation guidelines and all the features being deprecated in this blog post.

Reply by Note Hero Posted
  1. Back to top

    Reply

    by Note Hero

    Because the platform binding, leading to many versions of IE in use, version of the problem is very prominent!

    Share jQuery Reference Manual:
    www.heronote.com/files/jQuery.htm