Hot off the momentum of the jQuery Conference in Boston earlier this month, and based on the community’s valuable feedback, we’re releasing a new beta that incorporates further fixes and improves stability. The full list of fixes and features can be found below. We urge everyone to start testing this code in their applications, so we can make sure that there are no major problems before the final release.

You can get the code from the jQuery CDN:

• http://code.jquery.com/jquery-1.7b2.js

Please help us by dropping that code into your existing application. If you see something, say something. File a bug and mention that you’re testing against jQuery 1.7 Beta 2. If there’s a problem we want to fix it!

jQuery 1.7 Beta 2 Change Log

The current change log of the 1.7 Beta 2 release:

Ajax

• #9399: Deprecate jqXHR.success and jqXHR.error

Attributes

• #5479: removeAttr: remove multiple attributes
• #10176: Injected script tag is evaluated twice
• #10278: checkboxEl.attr(‘checked’) returns stale value after checkboxEl.click()
• #10429: IE7 – invalid procedure call or argument when calling removeAttr(‘contenteditable’);

Core

• #6485: Solution for HTML5 in IE
• #7102: Register jQuery as a CommonjS async module
• #9453: $.inArray does not support fromIndex
• #10478: Switch jQuery.isNaN to jQuery.isNumeric

Css

• #10267: IE8 and window is(‘:visible’) crashes

Data

• #7323: Allow removing multiple data keys at once with $.fn.removeData
• #8909: $(element).data() will scan all attributes more than needed.
• #8921: jQuery private data should stay private

Deferred

• #8856: Request: deferred.isUnresolved()
• #9033: try{ } finally{ } error in IE8
• #9398: Proposal for Improved Deferreds

Dimensions

• #9434: .outerWidth()/.outerHeight()/.innerWidth()/.innerHeight() should work on window and document

Effects

• #5684: Effects: exception in animation callback causes endless loop
• #6150: .stop sometimes doesn’t clear .delay
• #6641: Calling stop() within animation finished callback causes other animations to freeze
• #8685: Animations should keep track of animation state in order to properly address stacked animations
• #9280: Allow multiple effect queues for animate()
• #9548: animate does not work with fill-opacity css property for svg elements
• #10416: defaultDisplay returns block instead of table-row for a tr in FF
• #10445: Setting queue to true causes an error

Event

• #3368: event.metaKey should be assigned to event.ctrlKey on Non-Mac only
• #6170: jQuery(window).scroll(); causes IE* to scroll to 0,0
• #6319: Regression: stopPropagation inside change handlers in IE is incorrectly applied to keydown event
• #6386: support data argument for live events via “event.special.live.add”
• #6593: IE8: DOM 0 event handler called twice when a separate handler is attached via jQuery
• #6667: submit event doesn’t delegate in IE* under certain conditions
• #6903: special events need a way to determine whether they are being bound with .bind vs .live/.delegate
• #6942: JQuery.event.fix causes unnecessary reflows in IE when handling key events
• #7139: “hover” event alias should work for .bind as well as .live
• #7161: Submit event on a form element not unbound properly in IE
• #7444: Submitting form with “Enter” instead of button click on ie8 or ie7 triggers live submit event twice.
• #8157: Focusing an already focused text field will prevent the change event from firing in IE
• #8728: Event ‘mouseenter’ not firing when the element being left is removed on leaving
• #8789: Meta: Event Property Hooks
• #8858: Special events – _default method doesn’t have access to the `data` argument of the trigger method
• #8866: IE8 input[type=file] delegated change event files only on blur
• #8982: bind(“unload someOther”) => on unload, handler is not executed only once.
• #9069: when hover over a child of an element, mouseleave fires when using live or delegate
• #9279: delegate() bind does not handle mouseover/mouseout and mouseenter/mouseout correctly for selected elements
• #9393: Unify and DRY out event system
• #9593: Delegated submit event is not instanceof jQuery.Event in IE
• #9724: Infinite loop in trigger function when window.parentNode is a DOM element
• #9901: event.handleObj.namespace incorrect when using .delegate
• #9933: jQuery.fn.toggle() should store state in private data object
• #9951: Wrong order in .trigger() when DOM is modified in a handler
• #10375: Do not include `type` in jQuery.event.props
• #10438: Rename jQuery.event.propHooks => .fixHooks
• #10468: Remove deprecated jQuery.event.guid and jQuery.event.proxy
• #10489: Disconnected elements bubble to window on .trigger()

Manipulation

• #6782: carefully allow more strings to use innerHTML
• #7037: Duplicate mouseover and mouseout events added to cloned element.

Selector

• #3144: Inconsistent cross-browser results from .text() method
• #5637: Boolean (and Empty) Attribute Selectors Fail
• #6863: faster getText
• #7128: attribute selector is inconsistent between qSA and Sizzle due to use of DOM properties
• #8539: Sizzle cache collision in browsers without querySelectorAll
• #9261: Has Attribute not working in filter/children/siblings
• #9570: Selector $(‘form[name=”..”]’) returns zero elements in IE8 under some conditions
• #10178: $(window).is(“a”) >> Uncaught TypeError: Cannot call method ‘toLowerCase’ of undefined
• #10315: Sizzle ignores seed argument when using positional selectors

Support

• #5145: jQuery.support.opacity = false in the Chrome browser
• #6809: Add jQuery.support.fixedPosition

Traversing

• #10449: Function $(“#id”).closest(“.class”) returns element $(“#id”) itself if it has .class

If you hadn’t heard, jQuery Conference 2011 is taking place in Boston later this week. We’ve put together a little something we like to call jQuery 1.7 Beta 1 that we’ll be talking a lot more about at the conference. It’s got a lovely bunch of new features and significant bug fixes–more than 50 of them at last count.

You can get the beta from the jQuery CDN:

• http://code.jquery.com/jquery-1.7b1.js

Please help us by dropping this code into your existing application and letting us know if anything no longer works. Please file a bug ticket and be sure to mention that you’re testing against jQuery 1.7 BETA 1.

Also be sure to explore all the new features and see if your favorite pet-peeve bug has been fixed. If you wait until the final release to do your testing it will be too late!

As always, we want to encourage everyone from the community to try and get involved in contributing back to jQuery core. We’ve set up a full page of information dedicated towards becoming more involved with the team. The team is here and ready to help you help us!

Oh, you probably want to know what changed, right? Addy Osmani has made a great start with his recent post, so let’s cover the stuff that isn’t on his list.

New Event APIs: .on() and .off()

Over time, jQuery has evolved three ways to attach events to elements: .bind() , .live(), and .delegate(). Underneath it all, though, the three event APIs call the browser’s event system; that can lead to surprising interactions. For example, $(document).unbind("click") will remove all .live("click", ...) events, since those delegated events are attached to document. (This is also why you should use event namespaces.)

Our current event APIs aren’t going away soon, but to address the inconsistencies we’ve introduced a new and simple pair of event methods that can do the work of all three:

    $(elems).on(events, selector, data, fn);
    $(elems).off(events, selector, fn);

If a selector is provided, it’s a delegated event; otherwise it’s directly bound. All the features of the old APIs are there; for example events can be a space-separated string of event names and/or namespaces, or it can be an object where the keys are events and the values are event handler functions. Here are some examples of how the old methods map into the new ones:

Old API	New API
$(elems).bind(events, fn)	$(elems).on(events, fn)
$(elems).bind(events, { mydata: 42 }, fn)	$(elems).on(events, { mydata: 42 }, fn)
$(elems).unbind(events, fn)	$(elems).off(events, fn)
$(elems).delegate(selector, events, fn)	$(elems).on(events, selector, fn)
$(elems).undelegate(selector, events, fn)	$(elems).off(events, selector, fn)
$(selector).live(events, fn)	$(document).on(events, selector, fn)
$(selector).die(events, fn)	$(document).off(events, selector, fn)

Form Change and Submit Events in IE 6/7/8

These old Internet Explorer versions are likely to be haunting us for some time, so we’ve spent a while trying to improve their behavior. Event delivery performance has been greatly improved for them, but the biggest change is that we are using a different approach to fix their non-bubbling and broken form events. As a result we were able to greatly simplify and shorten the special events code. These events should work without any problems–even better than before, since we closed about a half-dozen related bugs–but please keep your eyes open for any unusual behavior.

Animation Improvements

Before version 1.7, if you stopped an animation before it completed it could create a situation where the element being animated would never return to its full size; it would essentially be stuck at the height that it was when the animation was stopped. We’ve fixed that by remembering the original dimensions before the animation starts so that they can be used later. This eliminates a major annoyance in using certain animations, particularly toggling ones.

.removeData() Enhancements

Addy mentioned this one as well, but the .removeData() API now lets you pass either a space-separated string of names or an array of names to be removed. Since spaces were previously allowed in data names, the code first checks for the exact name as you specified it before splitting the string on spaces. That way, no existing code should break as a result of this enhancement.

jQuery 1.7 BETA 1 Change Log

Here is a complete list of changes made for the 1.7 BETA 1 release.

Ajax

• #9399: Deprecate jqXHR.success and jqXHR.error

Attributes

• #5479: removeAttr: remove multiple attributes
• #10278: checkboxEl.attr(‘checked’) returns stale value after checkboxEl.click()

Core

• #6485: Solution for HTML5 in IE
• #7102: Register jQuery as a CommonjS async module
• #9453: $.inArray does not support fromIndex

Css

• #10267: IE8 and window is(‘:visible’) crashes

Data

• #7323: Allow removing multiple data keys at once with $.fn.removeData
• #8909: $(element).data() will scan all attributes more than needed.
• #8921: jQuery private data should stay private

Deferred

• #8856: Request: deferred.isUnresolved()
• #9033: try{ } finally{ } error in IE8
• #9398: Proposal for Improved Deferreds

Effects

• #5684: Effects: exception in animation callback causes endless loop
• #6150: .stop sometimes doesn’t clear .delay
• #6641: Calling stop() within animation finished callback causes other animations to freeze
• #8685: Animations should keep track of animation state in order to properly address stacked animations
• #9280: Allow multiple effect queues for animate()
• #9548: animate does not work with fill-opacity css property for svg elements

Event

• #3368: event.metaKey should be assigned to event.ctrlKey on Non-Mac only
• #6170: jQuery(window).scroll(); causes IE* to scroll to 0,0
• #6319: Regression: stopPropagation inside change handlers in IE is incorrectly applied to keydown event
• #6386: support data argument for live events via “event.special.live.add”
• #6593: IE8: DOM 0 event handler called twice when a separate handler is attached via jQuery
• #6667: submit event doesn’t delegate in IE* under certain conditions
• #6705: focus() causes focus event to be handled twice in IE8
• #6903: special events need a way to determine whether they are being bound with .bind vs .live/.delegate
• #6942: JQuery.event.fix causes unnecessary reflows in IE when handling key events
• #7139: “hover” event alias should work for .bind as well as .live
• #7161: Submit event on a form element not unbound properly in IE
• #7444: Submitting form with “Enter” instead of button click on ie8 or ie7 triggers live submit event twice.
• #8157: Focusing an already focused text field will prevent the change event from firing in IE
• #8728: Event ‘mouseenter’ not firing when the element being left is removed on leaving
• #8789: Meta: Event Property Hooks
• #8858: Special events – _default method doesn’t have access to the `data` argument of the trigger method
• #8866: IE8 input[type=file] delegated change event files only on blur
• #8982: bind(“unload someOther”) => on unload, handler is not executed only once.
• #9069: when hover over a child of an element, mouseleave fires when using live or delegate
• #9279: delegate() bind does not handle mouseover/mouseout and mouseenter/mouseout correctly for selected elements
• #9393: Unify and DRY out event system
• #9593: Delegated submit event is not instanceof jQuery.Event in IE
• #9724: Infinite loop in trigger function when window.parentNode is a DOM element
• #9901: event.handleObj.namespace incorrect when using .delegate
• #9933: jQuery.fn.toggle() should store state in private data object
• #9951: Wrong order in .trigger() when DOM is modified in a handler

Manipulation

• #6782: carefully allow more strings to use innerHTML
• #7037: Duplicate mouseover and mouseout events added to cloned element.

Selector

• #5637: Boolean (and Empty) Attribute Selectors Fail
• #7128: attribute selector is inconsistent between qSA and Sizzle due to use of DOM properties
• #9261: Has Attribute not working in filter/children/siblings
• #9570: Selector $(‘form[name=”..”]’) returns zero elements in IE8 under some conditions
• #10178: $(window).is(“a”) >> Uncaught TypeError: Cannot call method ‘toLowerCase’ of undefined
• #10315: Sizzle ignores seed argument when using positional selectors

Support

• #6809: Add jQuery.support.fixedPosition

jQuery 1.6.4 will be released soon, and we need your help with this release candidate to find any remaining bugs. We’re putting out a new version to address a few last-minute bugs that crept into the 1.6.3 release. With version 1.7 coming next month, we felt it was important to fix these bugs and finalize the 1.6.x line before making more extensive changes and feature additions.

Feel free to do your testing by including either one of these files (one minified and one uncompressed). If you find any important differences from 1.6.3, please file a bug as soon as possible and be sure to mention that you’re testing against jQuery 1.6.4 RC1. Our preferred venue for test cases is jsFiddle; you can just use the “jQuery (edge)” selection there.

• jQuery 1.6.4 RC1 Minified
• jQuery 1.6.4 RC1 Uncompressed

jQuery 1.6.4 RC1 Change Log

The current change log of the 1.6.4 release:

Data

• #10194: Data attribute names with single dash-surrounded letters cannot be accessed by the camel-case name

Event

• #10208: $(“form”).live(“submit”, fn) not fired from <button type=”submit”> in IE8

Support

• #10197: Bug with mime-type application/xhtml+xml in jquery 1.6.3

Please do file a bug report with a test case as soon as possible if you find problems, as described above. Blog comments or Twitter aren’t helpful bug reports!

jQuery 1.6.3 is almost ready to roll! We need your help with this release candidate to be sure we’ve got everything right.

Feel free to do your testing by including either one of these files (one minified and one uncompressed). Our preferred venue for test cases is jsFiddle; you can just use the “jQuery (edge)” selection there. If you need to report a bug and cannot use jsFiddle, please use the uncompressed version with your test case.

• jQuery 1.6.3 RC1 Minified
• jQuery 1.6.3 RC1 Uncompressed

Please test this release with your most treasured code. If you find any important differences from 1.6.2, please file a bug as soon as possible and be sure to mention that you’re testing against jQuery 1.6.3 RC1.

If you’re making a quantum leap from a much older version of jQuery, it’s possible that the differences you find are due to documented behavior changes introduced in a major-point release. Check your code with the released 1.6.2 version first to be sure the problem only exists in 1.6.3 RC1.

Highlights

Fix an XSS attack vector: User ma.la reported a common pattern that many sites are using to select elements using location.hash that allows someone to inject script into the page. This practice seemed widespread enough that we decided to modify the selector recognition to prevent script injection for the most common case. Any string passed to $() cannot contain HTML tags (and thus no script) if it has a “#” character preceding them. See the ticket linked above for more information and a test case.

No more animation “worm holes”: We had high hopes for the browser’s requestAnimationFrame API when we added support into version 1.6. However, one of the highest-volume complaints we’ve received since then relates to the way requestAnimationFrame acts when a tab is not visible. All the animations initiated when the tab is invisible “stack” and are not executed until the tab is brought back into focus. Then they all animate at warp speed! We’ve removed support for this API (which has no impact on the way you call jQuery’s animation features) and plan to incorporate it into a future version of jQuery.

Better handling of HTML5 data attribute names: The $().data() API serves double-duty, handling data for the internal use of jQuery and plugins in addition to reading initial values of HTML5 data- attributes. We’ve improved the ability to use HTML5 conventions such as converting camel-case to camelCase when needed. Remember, however, that the $().data() API only reads the HTML5 data- attributes initially, and does not keep subsequent data changes in sync with attributes for performance reasons. To update the actual attributes in the HTML markup, use .attr().

jQuery 1.6.3 Change Log

The current change log of the 1.6.3 release:

Ajax

• #9255: jQuery.parseXML error handling does not work in webkit browsers
• #9854: Pass statusText through instead of “normalizing” it
• #9887: jQuery.ajaxSetup may cause unnecessary memory usage
• #9970: Typo in ajax.js: status should be jqXHR.status?
• #10098: Encode comment-like Accept headers to avoid mobile carrier mangling

Attributes

• #9630: foo.contents().hasClass() returns incorrect value
• #9699: removeAttr(‘style’) does not consistently remove the style attribute in webkit
• #9719: removeAttr(‘disabled’) doesn’t change input’s color on IE6
• #9979: .prop(‘tabIndex’) returns inconsistent results for elements that have not yet set tabIndex
• #9980: Simplify the attr code by using getAttributeNode for everything in IE6/7

Build

• #9988: Minimal License Header in compressed jQuery

Core

• #9521: XSS with $(location.hash) and $(#) is needed?
• #9897: try-catch isPlainObject detection
• #10076: $.inArray crashes IE6 and Chrome if second argument is `null` or `undefined`

CSS

• #6652: Remove filter:alpha(opacity=100) after animation
• #9572: Support -ms-transform in .css() method
• #10021: Can’t add negative numbers using the relative-value syntax with .css() and .animate()

Data

• #8235: jQuery.data throws a script error in certain circumstances
• #9318: HTML5 data attributes has strange behaviour with if attribute names contain numbers
• #9413: $.fn.removeData does not remove data with a dash in a name
• #9779: Allow non-null|undefined evaluation of data property values
• #9794: jQuery.fn.data() correctly handle access to arbitrary data property values
• #10016: Cannot retrieve “false-y” values under key names with dashes using jQuery.data method
• #10080: unload from frame’s window breaks in IE8

Dimensions

• #10123: .width() can return a float in Firefox 6

Effects

• #9381: Animations halt when the browser is out of focus due to requestAnimationFrame
• #9678: setInterval cleared by animation

Event

• #7071: Accessing the ‘type’ property on VML elements fails on IE during submit special handler

Manipulation

• #9587: Cloning a div with an object causes error in IE8

Support

• #9634: Visible “t” character in upper left corner during support.js init
• #9823: IE 8 crashes when using background-image on BODY in css
• #9964: test/support.js module strictEqual typo
• #10029: $.support.scriptEval removed, but still included in documentation

Please do file a bug report with a test case as soon as possible if you find problems, as described above. Blog comments or Twitter aren’t helpful bug reports!

jQuery 1.4.4 is now out! This is the fourth minor release on top of jQuery 1.4 and lands a number of fixes for bugs including some nice improvements over 1.4.3.

We would like to thank the following community members that provided patches, input and their time towards this release: Rick Waldron, Dan Heberden, Alex Sexton, Colin Snover.

Along with the following members of the jQuery core team: John Resig, Dave Methvin, Karl Swedberg, Paul Irish.

We also thank our bug triage team who assisted in narrowing down some of the important fixes needed for this release: Colin Snover, Rick Waldron, Addy Osmani, Alex Sexton, Adam Sontag, Dave Methvin, Mike Taylor, Aaron Boushley, Jitter and John Resig.

Downloading

As usual, we provide two copies of jQuery, one minified and one uncompressed (for debugging or reading).

• jQuery Minified (26kb Gzipped)
• jQuery Regular (179kb)

You can feel free to include the above URLs directly into your site and you will get the full performance benefits of a quickly-loading jQuery.

Additionally you can also load the URLs directly from Microsoft and Google’s CDNs:

Microsoft CDN: http://ajax.microsoft.com/ajax/jQuery/jquery-1.4.4.min.js

Google CDN: https://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js

General Improvements

We’ve made a number of improvements with this release, many of which have fixed bugs that were highlighted by the jQuery Community. For the complete list of changes, see the section below marked ‘Changes’ for more information.

New Features

All new features and changes can be found in the jQuery API documentation for 1.4.4.

.fadeToggle()

In an attempt to further unify the methodology across our API, we’ve introduced a new method to Effects called .fadeToggle(). We already have existing toggle methods in our API for sliding (.slideToggle()) and toggling classes (.toggleClass()) and it made sense for us to extend the availability of a built in toggle to fading effects as well. See the API documentation on .fadeToggle() for more information.

Changes

What’s Been Updated?

There are a few areas in jQuery that have seen changes since 1.4.3 was released:

• (New) Added a new animation method, .fadeToggle()
• (Enh) Calling .data() with no arguments now includes data from HTML5 data- attributes (#7222)
• (Enh) Moved jQuery.props from support.js to attributes.js (#6897)
• (Enh) .width() and .height() now report the width and height of hidden elements (#7225)
• (Bug) stopImmediatePropagation was not being honoured in live/delegate event handlers (#7217)
• (Bug) Fixed an issue where host and protocol were not compared case-insensitively when determining whether an AJAX request was local or remote (#6908)
• (Bug) Fixed an issue where the “clone” variable was not being declared correctly (#7226)
• (Bug) Fixed a bug where we only change the ID on nodes that don’t already have an ID for rooted qSA (#7212)
• (Bug) Limited the scope of the CSS ‘auto’ change to just height/width (#7393)
• (Bug) Fixed a bug to ensure that unquoted attribute selectors are quoted (allowing them to go into qSA/matchesSelector properly). Fixes (#7216)
• (Bug) Fixed a bug to ensure that if additional load events are triggered (eg. an iframe being dynamically injected in DOM ready) the ready event isn’t triggered twice (#7352).
• (Bug) Fixed a condition that prevents attr from working on non-Element nodes (#7451).
• (Bug) Changing an HTML5 data attribute after calling .data(‘foo’) no longer causes .data(‘foo’) to also change (#7223)
• (Bug) Fixed a bug where Opera didn’t give height/width of display: none elements with getComputedStyle but did with currentStyle – fall back to that if it exists added.
• (Bug) Fixed a bug to ensure accessing computed CSS for elements returns ‘auto’ instead of ” consistently (#7337)

It also fixes a number of regressions in 1.4.3. One that caused:

• (Bug) JSONP calls to fail when cleaning up after a callback (#7196)
• (Bug) .removeData() to fail (#7209)
• (Bug) “ready” events to fire twice when added using .bind(“ready”, foo) (#7247)
• (Bug)  .css(‘width’) and .css(‘height’) to return 0 or negative values when trying to get the style of a hidden or disconnected element (#7225)
• (Bug) the attribute not equals selector ([foo!=bar]) to not work in Firefox (#7243)
• (Bug) find() to fail when selecting from forms containing inputs named “id” (#7212)
• (Bug) .children(selector) to fail on XML documents (#7219)
• (Bug) child (>), next sibling (+), and previous sibling (~) selectors to fail when combined with non-CSS pseudo-selectors like :last (#7220)
• (Bug) an error “handler is null” to be raised when passing null as the event handler (#7229)
• (Bug) it to be impossible to include a content-body with DELETE requests (#7285)
• (Bug) it to be impossible to include data with HEAD requests (#7285)
• (Bug) an issue where IE was firing click events on disabled elements when using live/delegate (#6911)
• (Bug) .show() to fail if .hide() was first called on an already-hidden element (#7331)
• (Bug) .show() to fail if an element was hidden in a stylesheet, then had .css(‘display’) manually set prior to calling .show() (#7315)

Backwards-incompatible changes in jQuery 1.4.4

The .width() and .height() methods no longer return 0 when inspecting an element hidden using ‘display: none’. To determine if an element is hidden, always use .is(‘:hidden’).

and that’s it!. jQuery 1.4.4 is now out so feel free to update your projects to use the latest version. We welcome any and all feedback from the community.

What Features Would You Like To See In jQuery 1.5?

Now that jQuery 1.4.4 is out, we’re starting the process of planning our next major release and we would like the community’s help in deciding what features we should include. The process for suggesting a feature is quite straight-forward; here’s what you need to do:

1. Think of a feature you would like included in jQuery 1.5
2. Create a new ticket for that feature in our [bug tracker] if one does not already exist
3. Send your nomination by filling out the [jQuery 1.5 feature nomination form]

Thats it! In a couple of weeks the jQuery team will be sitting down to review all nominations. The features that we think would benefit the majority of the community will be added to our roadmap.

We’re aiming to release jQuery 1.5 early next year and we appreciate any help you can provide in letting us know how we can improve it for you. We look forward to hearing your ideas and feature requests.

Today, we’d like to announce that we’ve moved the Official jQuery Podcast off the jQuery blog and onto it’s own site at http://podcast.jquery.com.

We felt that with a weekly blog post for each episodes show notes the podcast was taking over the blog.  Some of the community members thought the same way.  We’ve been working on porting over the existing posts and making the new podcast site easier to use for our listeners.

Each episodes show-notes are now streamlined to give you a quick introduction about what the show is about followed by all the links that were mentioned in the show.  We also have the ability to play the show from the post with an embedded player as well as easy links to download and subscribe.

We also have a easy contact form that will allow you to contact the podcast directly.

We’ve cleaned up the jQuery blog and removed the old show notes and put in place URL redirects so old urls will still go to the right post on the new site. While we are talking about the blog, we’d like to know what would you like to see more of on the jQuery blog?  Currently we’ve been using the blog to post news about the project and upcoming events.  What else can we post to help you out?  We’d love to hear your ideas.

Special thanks goes out to Doug Neiner for helping out with design and coding, also, would like to thank Jonathan Sharp for setting up the site and getting the URL redirects in place.

Let us know what you think of the new podcast site and don’t forget to keep listening to the show.

Mobile web development is an emerging hot topic in the web development community. As such, the jQuery Team has been hard at work on determining the strategy and direction that the jQuery Project will take. Today, we are proud to announce the jQuery Mobile Project. We’ve launched a new site at jquerymobile.com that publicly outlines our strategy, research and UI designs.

As always, we want to hear from you.  We’ve created a new Mobile jQuery forum to collect feedback from the community.  Please feel free to join in on the discussion and read more in the announcement.

The jQuery Project is very excited to announce the final schedule and speakers list for our first-ever San Francisco Bay Area conference. The conference will be held at the Microsoft Silicon Valley Research Center in Mountain View, California on April 24th and 25th, 2010.

Speakers include: John Resig, Scott González, Steve Souders, Nicholas Zakas, John Nunmaker and most of the jQuery team to name a few.

Registration for the jQuery Conference 2010: San Francisco Bay Area is still open! You still have a chance to register for this great event!

Get your ticket today.

A brief synopsis of some of the content that you’ll be able to expect:

• jQuery
• jQuery UI
• jQuery Plugins
• Complex Application Development
• jQuery Case Studies

In addition to two days of jQuery sessions, for the first time we’ll be adding an additional day of jQuery training, prior to the main event. The training will be provided by appendTo and focused on helping you and your team get up to speed on jQuery prior to attending the conference. The training will cover the following topics:

• Introduction to jQuery
• Finding Something
• Doing Something With It
• Chaining
• Introduction to jQuery UI
• Implementing jQuery UI Widgets

The training will be held on April 23rd at the Microsoft San Francisco offices in downtown San Francisco; tickets will cost $299. All proceeds from training go to the jQuery Project.

Get your ticket today.

In case you’re not following along with the 14 days of jQuery, here’s a summary of what has been released for days 8-14.

Highlights

On Day 12, the jQuery team released jQuery 1.4.1, the first bug release to jQuery 1.4. jQuery 1.4.1 is now the latest release of jQuery; take a moment to review the 1.4.1 release notes.

On Day 13, the team announced the new jQuery Meetups site. We want to help foster local meetups and eventually try to provide more resources to your groups.

On Day 14, the jQuery UI team released jQuery UI 1.8 Release Candidate 1. The team would love you to test and provide feedback with bugs or comments in the jQuery UI Development forum.

Full Recap

Day 8

• The jQuery Project
• jQuery.org

Day 9

• jQuery Workshop Giveaway
• jQuery Podcast Episode 8: api.jquery.com
• jQuery 1.4 Hawtness #3, with Paul Irish
• jQuery API Key Navigation

Day 10

• jQuery 1.4 Hawtness #4, with Paul Irish

Day 11

• Evented Programming with jQuery, Yehuda Katz
• Behind the 14 Days of jQuery

Day 12

• jQuery 1.4.1 Released
• jQuery 1.4 Hawtness #5, with Paul Irish

Day 13

• jQuery Meetups
• jQuery 1.4 Hawtness #6, with Paul Irish
• Paul Irish and Dave Methvin Join the jQuery Team

Day 14

• jQuery UI 1.8rc1

Sponsors and Donations

Again, events like these are not possible without support from our great sponsors and from you, the jQuery Community. We’d like to thank everyone who has donated during this campaign. We received donations from 653 people, and we are truly grateful to all who contributed. If you missed the campaign, you can still let us know how much jQuery makes your life easier by sending a tax-deductible donation or by showing our sponsors some love for their support.

Netflix

Netflix, Inc. (NASDAQ: NFLX) is the world’s largest online movie rental service, with more than 11 million subscribers. For only $8.99 a month, Netflix members can instantly watch unlimited movies and TV episodes streamed to their TVs and computers and can receive unlimited DVDs delivered quickly to their homes.

JupiterIT

Jupiter provides expert web application development, support services, and training. Committed to open source, Jupiter collected its global experience delivering enterprise JavaScript applications and made it publically available as JavaScriptMVC.

appendTo

appendTo, the jQuery company, delivers industry-leading jQuery training and support services to the web development community and corporations worldwide. Leveraging the power of the Write Less, Do More JavaScript library and the vast experience of jQuery Team Members, appendTo is at the forefront of propelling the jQuery movement into the next generation of open source technology advancements

Oxide Design

Oxide Design Co. is a communications and information design firm. We specialize in corporate identity, brand strategy, packaging, print, and web site design. We clarify ideas to create effective design.

Fusionary

We are Fusionary, an award-winning web and interactive studio. We’ve been creating things online since 1995 and our clients love us.

The team hopes you enjoyed this online conference celebrating the 1.4 release of jQuery. We would love to hear your feedback. Please submit your feedback in this thread on the new jQuery Forum.

jQuery 1.4 Alpha 2 is released! This is the second alpha release of jQuery 1.4 (alpha 1 was released previously). The code is stable (passing all tests in all browsers we support), feature-complete (we’re no longer accepting new features for the release), and needs to be tested in live applications.

Grab the code:

• Regular: http://code.jquery.com/jquery-1.4a2.js
• Minified: http://code.jquery.com/jquery-1.4a2.min.js

NOTE: If you’re using jQuery 1.4a2 and you run into an error please make sure that you’re using the regular version of the code, it’ll make it easier to spot where the error is occurring.

How can I help?

To start, try dropping the above un-minified version of jQuery 1.4a2 into a live application that you’re running. If you hit an exception or some weirdness occurs immediately login to the bug tracker and file a bug. Be sure to mention that you hit the bug in jQuery 1.4a2!

We’ll be closely monitoring the bug reports that come in and will work hard to fix any inconsistencies between jQuery 1.3.2 and jQuery 1.4.

With your input we should be able to produce a solid release. Right now we’re looking to push out at least one beta around the beginning of the new year and a final release candidate early in January. The final release will occur on January 14th, coinciding with jQuery’s 4th birthday. Thanks for your help in reviewing jQuery 1.4a2!