Monday, March 30th, 2009

Prototype 1.6.1 RC2: IE 8 Here we come

Category: JavaScript, Library, Prototype

Andrew has posted on Prototype 1.6.1 RC 2, a new release that “is fully compatible — and fully optimized for — Internet Explorer 8’s “super-standards” mode. In particular, Prototype now takes advantage of IE8’s support of the Selectors API and its ability to extend the prototypes of DOM elements.”

New Features

Full compatibility with Internet Explorer 8. Juriy has spearheaded the effort to replace most of our IE “sniffs” into outright capability checks — making it far easier to support IE8 in both “super-standards” mode and compatibility mode.

  • Element storage, a feature announced previously. Safely associate complex metadata with individual elements.
  • mouseenter and mouseleave events — simulating the IE-proprietary events that tend to be far more useful than mouseover and mouseout.
  • An Element#clone method for cloning DOM nodes in a way that lets you perform “cleanup” on the new copies.
  • What’s been improved?

    • Better housekeeping on event handlers in order to prevent memory leaks.
    • Better performance in Function#bind, Element#down, and a number of other often-used methods.
    • A number of bug fixes.

    In addition to the code itself, the 1.6.1 release features Prototype’s embrace of two other excellent projects we’ve been working on: Sprockets (JavaScript concatenation) and PDoc (inline documentation). Sprockets is now used to “build” Prototype into a single file for distribution. PDoc will be the way we document the framework from now on.

    Great stuff.

    Posted by Dion Almaer at 12:15 am
    1 Comment

    3.8 rating from 49 votes

    1 Comment »

    Comments feed TrackBack URI

    Can anyone explain why they decided to implement _prototypeUID as a one element array rather than just a number? It seems that they have changed their mind since the announcement ( and I am just curious as to why.

    Comment by devnullio — March 30, 2009

    Leave a comment

    You must be logged in to post a comment.