Hosting and Configuring the jQuery Servers

Posted on by

The other day, we posted about our new content workflow, but we didn’t get into how all that content is actually served. Believe it or not, jQuery doesn’t just run on jQuery.

The servers

The servers themselves are hosted at Media Temple. We have been using their VPS services for many years to host all the things we need to host, of which there are a surprising number. We use over a dozen different servers (of various sizes) hosting everything in the jQuery network including many different web sites, applications and services vital to the community and development team. The reliability of the Media Temple VPS services and network for our infrastructure has been fantastic.

The setup

We couldn’t manage all of the servers without Puppet. Puppet is a configuration management tool that makes it really easy to express server configuration in a simple scripting language. Tasks like adding a domain to the Nginx configuration can be annoying, and hard to track changes using conventional methods. Using Puppet lets us store all the server configuration needed in a git repository, and deploy new machines very easily.

Another product that really shines in our setup is Nginx. Nginx is an open source web server focused on delivering the best performance possible. On our busiest Media Temple Dedicated Virtual server around peak times, Nginx handles about 300 HTTP requests per second, of which about 30 are serving pages from WordPress via php-fpm. Nginx’s built in fastcgi_cache handles a lot of that load, and more like 2 or 3 requests per second actually make it to PHP.

Thanks for the support!

Keeping a network of servers running to support a community as large as jQuery’s is a big job. To help ensure everything runs smoothly, we rely on jQuery Infrastructure team members Adam Ulvi and Ryan Neufeld, and for server and network-related issues we count on prompt and helpful support from the Media Temple team.

To celebrate their 7 years of serving the jQuery community, Media Temple is extending a special offer on their VPS and Grid Hosting. For the next 5 days, get 50% off an annual purchase of a Grid or VPS (up to level 3) service with the code LovejQuery50.

Speaking of support, if you need any support with jQuery, or the related web sites and services, check out one of our IRC channels on freenode.

Getting from GitHub to WordPress

Posted on by

Maintaining an open source project as big as jQuery requires the use of various software and services. Two of the products we rely on and enjoy the most are GitHub and WordPress.

We’ve been using and loving Git and GitHub for years now. The community collaboration has been phenomenal. We’ve seen a massive uptick in community-provided bug fixes, refactors, new features, etc. Even within the team, the services provided by GitHub have provided a huge productivity boost. Forks and pull requests provide a great mechanism for sharing code and peer code reviews. The interface renders almost every file exactly how we want it to, especially Markdown. The API and service hooks provide a great way to automate various tasks.

Even longer than we’ve been using GitHub, we’ve been using WordPress to manage our various web sites. We have a surprisingly large number of them. Between project sites, API documentation, tutorials, contribution guides, events, and organization sites, the number of web sites we maintain rivals the number of code projects we maintain. WordPress provides tools which make managing this many sites with a common brand almost as simple as maintaining just one site with shared users, theme inheritance, and a great plugin architecture, providing even more hooks than GitHub.

The missing pieces

Unfortunately, our WordPress experience lacked all the collaboration tools and workflow we love. Only a few people had access to edit content, and collaboration without pull requests is painful. Managing content on api.jquery.com was an even bigger hassle because of our XML based workflow, which the WordPress editor clearly wasn’t designed for.

While GitHub has tons of tools that we love, and they even have GitHub Pages, it lacked the infrastructure we need for managing our site content. GitHub Pages have no built-in features and can’t have any server-side processing. Features like search and commenting either need to be added per site via client-side JavaScript or can’t be implemented at all.

Bringing it all together

In order to resolve these issues, we decided to find a way to bring these two products together and get the best of both worlds. It started off pretty bumpy, but we managed to do just that! Things started to really pick up when we got the support of WordPress’ Lead Developer Andrew Nacin. Nacin played a key role in getting our new infrastructure set up and ensuring we were using WordPress as efficiently as possible. With his help, and the help of a few new projects – such as node-wordpress, grunt-wordpress, and grunt-jquery-content – we were able to build exactly what we wanted.

We now manage our WordPress theme in jquery-wp-content, and the content for all of our sites are stored and managed in individual repositories on GitHub. Storing the content of each site on GitHub gives us all the benefits of tracking tasks in issues, discussions on pull requests, visual diffs for changes, etc. The content of each page is generated by grunt-jquery-content from HTML, XML or Markdown source depending on the repository. This content is then synced to WordPress using grunt-wordpress. Just like our code, all of our site content is open source and released under the terms of the MIT license, with the exception of our branding which is not licensed for use by others.

We’re now powering a dozen and a half sites with this new process, averaging 20 contributors per site. Our most popular sites for community contribution are learn.jquery.com which is nearing triple digits and api.jquery.com which currently has 50 contributors. We’re averaging 40 pull requests per site as well, showing just how beneficial this new workflow has been for the team and the community. If you’d like to join in on this community effort, you can read more about our process and how to get involved on our contribution site and help make jQuery better for everyone.

jQuery 1.11.0 RC1 and 2.1.0 RC1 Released

Posted on by

We’re just about ready for the final release of jQuery 1.11 and 2.1! Before we release, we’d like you to sanity-check our work. It will save us both a bunch of work if you check things out now, rather than waiting for a release. If something’s not right, we can fix it before millions of people have to deal with it!

Testing is easy, just use one of these files on the jQuery CDN:

We’ve also published the files on npm for those of you using that for dependency management. This version should work properly with browserify.

This version is mainly about fixing bugs and supporting more dependency managers, so you shouldn’t expect to see compatibility issues if you’ve already migrated to 1.9 or higher. But that’s why we’re putting out a release candidate, we want this to be as stable as possible. If you do see problems, please report them at bugs.jquery.com.

Go forth and test!

Changelog

Common to both jQuery 1.11 RC1 and jQuery 2.1 RC1

Ajax

Attributes

Build

Core

Css

Data

Effects

Event

Misc

Selector

Support

jQuery 1.11 RC1

Ajax

Core

Effects

Support

jQuery 2.1 RC1

Ajax

Build

Core

Event

The jQuery Foundation and Standards

Posted on by

Most web developers think about jQuery in terms of its roots, as a library that tries to bring sanity to a disparate set of APIs and quirks that vary from browser to browser. Although that’s one of the things that jQuery was built to do, and still does, it’s not the only thing. jQuery defines a useful API that makes it as easy to work with one element as it does for a dozen. jQuery shortens verbose DOM API names and removes tedious boilerplate code, making it easier to write and to read code. jQuery adds functionality beyond the standard APIs for the work that web developers often need to do.

In short, jQuery isn’t just an API repairman for browsers. To the extent that we need to fix problems, we do it. But we’re even more interested in getting browsers to fix their problems, and in shaping future standards to avoid problems, so native APIs will work properly from the start. Then we can all build useful functionality on top of that solid foundation.

jQuery team members bring plenty of real-world experience that guide standards in the right direction. The earliest example of this is the querySelectorAll method, where John Resig pointed out that the implementation wasn’t quite what JavaScript developers needed. Unfortunately in the case of querySelectorAll, it was too late to do anything to fix the problems.

How jQuery Can Shape Standards

In order to provide input into emerging standards, the jQuery Foundation joined the World Wide Web Consortium (W3C) and ECMA International last year. In fact, it’s one of the main reasons the Foundation was formed. W3C and ECMA members tend to be representatives of the companies that make browsers and commercial software. We believe that we bring the voice of the rank-and-file web developer to the standards process.

Yehuda Katz and Rick Waldron have been active in the ECMA TC39 group, which defines the language officially known as EcmaScript but that we know as JavaScript. Rick’s excellent meeting notes can give you an inside view of the deliberations that go on during their in-person meetings.

Scott González and Kris Borchers have been working to refine the Pointer Events standard. It brings simplicity, regularity, and sanity to the handling of pointer technologies so that developers don’t have inconsistent (and conflicting!) event models for touch and mouse. During the transition, developers will be dealing with three pointer models–mouse, touch, and pointer. jQuery and jQuery UI want to simplify this transition to the standard.

Julian Aubourg has been participating on revisions to the XMLHttpRequest standard, a position for which he’s been battle-tested by jQuery’s $.ajax implementation. Knowing all the problems that jQuery has worked around provides him with experience to avoid the same problems in the future.

Scott González and TJ VanToll have been active in helping to define HTML5 input types such as <input type=”date”>, providing practical input based on experience with jQuery UI. TJ’s talk at the Portland jQuery Conference does a great job of covering the pitfalls of using HTML5 input types today, and emerging standards like Web Components that could make things easier for web developers.

The jQuery Foundation is also a strong advocate of accessibility; we want to make it easy for web developers to reach all users including those with vision or motor impairments. The W3C addresses those issues through the Web Accessibility Initiative, and specifically with Accessible Rich Internet Applications (ARIA). jQuery UI widgets are incorporating ARIA attributes, and Foundation member Deque Systems has sponsored several events on jQuery accessibility issues.

Finally, we coordinate and pass along bugs reported to jQuery that are due to standards violations in a particular browser. With most browsers updating every few months, it often doesn’t make sense for jQuery to incorporate large and complex bug fixes for temporary problems. But we’re committed to getting them fixed by the browser makers as soon as possible.

A Standards-Driven jQuery Future

jQuery isn’t a highly opinionated framework that demands control over all the DOM. In most cases you can (and often should) use the DOM APIs alongside jQuery. That was always the intended design; you can see it in aspects like the this object inside an event handler being a DOM element, not a jQuery object. About the only place where jQuery requires control is when elements in the DOM are replaced via methods like .html() or removed with a method like .empty(), so that any associated jQuery data can be cleared out.

Similarly, the built-in HTML5 input types can coexist with jQuery UI input widgets. jQuery UI is committed to providing user interface widgets that provide great functionality without sacrificing accessibility, inherently supporting standards such as ARIA.

The jQuery Foundation wants standards-based APIs and cutting-edge JavaScript features to be usable directly by developers. The good news is that the community is making good progress on that goal, and jQuery team members are helping through our participation in the standards process. Yet the continuing evolution of web standards and practices, combined with a vibrant third-party ecosystem of plugins and knowledge, still provide compelling reasons to use jQuery. Web developers deserve to have the best of both.

jQuery Austin Speaker Lineup

Posted on by
jQuery Conference Portland logo

With just over a month until jQuery Austin starts, I wanted to take a few minutes to point out the highlight of our conference program: our talks! With a single-track conference, it’s our job to select individual talks that will appeal to the entire conference audience. At the same time, we want to make sure we cover a broad range of subjects related to jQuery and front-end engineering so that every attendee can take home something that will make a difference in their day-to-day development. Those were our goals with our Call for Papers, and we hope you’ll agree our 20 selections fit the bill.

jQuery

One of the main focuses of #jqcon is to bring you the latest on what’s going on in the jQuery libraries, and there’s no one better for that than keynote speakers Dave Methvin and Scott González, development leads for jQuery and jQuery UI. Dave will be talking about more than just recent changes to jQuery core; he’ll be delving into how to diagnose what does (and doesn’t) cause performance woes in modern web apps. And with the jQuery UI and jQuery Mobile projects merging, you’ll want to be sure to hear Scott tell what the future has in store.

As increased modularity comes to jQuery, Timmy Willison will describe how and why we’re making the switch to AMD in core, and how to leverage these forthcoming changes in your apps. Julian Aubourg is going to take a dive into Deferreds and Promises, which have been proven to be a useful tool for managing asynchronous code, even since before their incorporation into jQuery a few years ago.

Mobile

We’re excited to have a number of talks on taming the burgeoning beast that is mobile development. Alex Schmitz will be reviewing the results of the Mobile team’s serious look at the performance of jQuery Mobile for the upcoming 1.4 release, and outline new features that have been added with performance in mind, and Asta Gindulyte will examine how to use jQuery Mobile across a wide variety of screen sizes, from phones right on up to televisions.

Figuring out how to serve the right images to your application’s users across devices and bandwidths has been one of the more interesting discussions in web development for the last year or two, and that’s why we’ve brought Christopher Schmitt to help you make sense of it all. Building applications that work offline is another challenge, and Seth Hallem will explain how to persist, search, update, and display data in HTML5 mobile apps.

Application Development

Debugging is the constant task of software development, and Brian Arnold will be walking us through the constantly-improving tools that can help improve your skills in this dark art. Sometimes, apps appear to work fine until they get into the hands of users who require a screenreader, so Jörn Zaefferer will be giving a primer on the important subject of how to make your web application accessible to all users.

Client-side MVC frameworks are certainly all the rage these days; after having talks on Backbone and Ember at jQuery Portland, we’re thrilled to bring AngularJS into the mix, with Burke Holland bringing you up to speed on directives, one of the framework’s coolest features. If you’ve been using MVC frameworks, one question that you’ve likely wrangled with is where to draw the line between reusable UI widgets and custom application code – which just happens to be one of the subjects Richard Lindsey will be presenting in his discussion of the jQuery UI Widget Factory.

Front-End Ops

Web applications are continuously becoming more JavaScript-centric, bringing increased rigor to the client-side. Grunt has taken off as a popular tool for building and minifying code, and Aaron Stacy‘s talk will explore how to use this JS task runner for even more. Many more developers are recognizing the importance of writing unit tests, and Travis Tidwell will be in Austin to help you incorporate running tests into your deployment process with PhantomJS.

All the technology in the world doesn’t change the fact that web applications are still written by human beings, and Monika Piotrowicz will analyze how we can improve our workflows to better accommodate all the different people who are involved and perhaps even build better products! The jQuery Foundation itself is one organization where we’ve made significant changes to how we work in order to get more developers involved in the project, and Anne-Gaelle Colom will be on hand to detail her experiences as she’s grown to become the Documentation lead for jQuery Mobile.

mind === blown

The open web platform continues to evolve and bring with it exciting new possibilities for what we can do in the browser. Jenn Schiffer will enlighten you on the canvas tag and how it can let you use your coding abilities to be creative and make art, and Vlad Filippov will bring this discussion into a full three dimensions as he shows off voxel.js, a WebGL-based toolkit for creating Minecraft-like worlds and interactive visualizations.

If you’ve got pockets and a phone that vibrates, then you’re surely aware of the utility of push notifications, and Kris Borchers will explain the finer points of their journey to the web platform. Web Components are another emerging spec that have the potential to change how we develop and share reusable widgets, and Juan Pablo Buritica will illuminate the current state of affairs and show tools that will let developers get started writing more modular code today.

Join Us

With so much in store, we hope you’ll head deep in the heart of Texas with us on September 10 and 11! Head on over to the conference site to read more about the program and buy your tickets today. In fact, we’re celebrating the renaissance of our RSS feed with $25 off coupon for anyone who uses the coupon code JQBLOG until we run out of tickets!

If you’re able to attend #jqcon, you’ll probably want to stay within walking distance of the Austin Convention Center in our room blocks at the Hyatt Place and Radisson hotels, especially if you want to be able to explore downtown Austin and rub elbows with your fellow attendees.

If you have any questions, always feel free to get in touch with us on Twitter or via e-mail. If not…see you there!

Live From Portland, It’s jQuery!

Posted on by

Later this week, jQuery Conference is returning stateside for the first time in 2013, and we’re excited to announce another first: inspired by the mighty Willamette River running through Portland, we’re bringing you our first-ever live stream! No matter where you are in the world, you’ll be able to take in both days of #jqcon and the pre-conference Bocoup training. Doing a live stream comes with its own challenges and complexities, so we are selling tickets for each stream, and wanted to take a moment to walk you through your options.

Conference Live Stream

A ticket for the conference live stream costs $149, which entitles you to both tracks on June 13th and 14th. However, jQuery Foundation members get free tickets to the live stream. Membership in the foundation is as little as $100 annually (and you get a t-shirt!), so now’s a great time to join the foundation, show your support for jQuery and learn a whole lot! If a bunch of folks at your company would all like to attend, we’re also selling Group tickets for $749.

Training Live Stream

In addition, live streaming tickets are available for the one-day Bocoup trainings on June 12th for $299, with an additional $50 discount for jQuery Foundation members. You can choose to attend either the Advanced jQuery or Front-end Fundamentals classes. Group tickets are available for $999.

How It Works

Once you buy your live stream tickets, the morning of each event you’ll receive an e-mail with your unique link to the stream. Click on it! (Or simulate a mouse click using the whole document.createEvent song and dance, if you’re so inclined.)

Odds and Ends

We still have a few late-bird tickets remaining, and we’ve just announced we’ll be hosting a party on June 13th thanks to our friends at Jive Software, so if you’re still on the fence, hopefully you just fell off (gently)! Whether you’re joining us in person or on the stream, we’re looking forward to three days of fun and learning, and hope you are too.

As always, follow @jqcon for detailed conference updates, and join us in the #jqcon channel on Freenode to chat with fellow attendees around the room, and around the world.

jQuery Migrate 1.2.0 Released

Posted on by

The latest version 1.2 of the jQuery Migrate plugin is here! It can be used with either jQuery 1.9 or jQuery 2.0 to provide diagnostics and remedial help for plugins that haven’t been updated since jQuery 1.9 was released earlier this year. Believe me, this plugin can really make your life easier; if you’ve been afraid of upgrading jQuery, this plugin can cure that irrational software phobia.

The major change in this version is that we’ve re-closed a cross-site-scripting (XSS) hole that was fixed in jQuery 1.7 and reintroduced by the plugin. Essentially, any use of $("#... <tag>") will now always be interpreted as a selector and not as HTML. This is due to some developers using $(window.location.hash) and not realizing that an attacker can often control the contents of the hash on the URL to run code. Always assume that any data you get from an external source may contain harmful content!

You can find this latest version of the jQuery Migrate plugin on jQuery’s CDN:

Using the plugin is as easy as including it right after the version of jQuery you are using, for example:

<script src="http://code.jquery.com/jquery-1.9.1.js"></script>
<script src="http://code.jquery.com/jquery-migrate-1.2.0.js"></script>

Complete instructions and a complete list of the diagnostics given by the plugin are located in the plugin project’s README file.

A full list of all changes are in the issue tracker. Many thanks to Igor Kalashnikov and Max Riviero for their help on this plugin!

jQuery Learning Center: Welcome!

Posted on by

Today I’m proud to announce the official opening of the jQuery Learning Center, a community-driven site dedicated to helping people learn about jQuery, JavaScript and front-end development. The goal is to provide a resource that can fill in the gaps that necessarily exist between reading about APIs and actually understanding how to use jQuery effectively. We know a lot of people scour the web each day for this type of information, and we hope the Learning Center can serve as a dependable place for our users to turn.

The Learning Center will continue to evolve, but it would not be what it is today without Rebecca Murphey’s jQuery Fundamentals, which she donated to the jQuery Foundation to form its original nucleus. (Thanks Rebecca!) For this initial launch, we’ve worked to supplement this with information about jQuery UI and jQuery Mobile, features that have been added to jQuery in the interim, and other blog posts and articles from other authors. We’ve also ported over most of what remained on docs.jquery.com, as the Learning Center is indeed intended to be its replacement: documentation that anyone can use — and edit!

There are lots of folks in the jQuery community who like to share their knowledge with others and spend a lot of time writing articles and giving advice, hoping only that it helps someone else understand how to make a decision or get out of a jam. The jQuery Learning Center is for you too. We hope that it will empower those of you who already do this (and those who haven’t — yet) to reach the right audience: the people looking for it! The Learning Center is the latest in the jQuery Foundation’s series of open content sites, so all of the articles are written in Markdown and the entire site is open source. Whether you’ve got a new article you’d like to get published or just notice a typo, the Learning Center is certainly one area of jQuery that’s open to all sorts of new feature requests!

You can find out more about the jQuery Learning Center, and if you’re interested in helping out, you should definitely take a look at our Contributing Guide. We’ll continually seek to flesh out the subject matter on the site, so whether you’ve already got a great idea, an old StackOverflow answer that you always thought “should be in the docs,” or want to take a look at the existing issues for inspiration, there’s sure to be something you can dig into!

We hope the new Learning Center will be a useful new reference for users and authors alike, and welcome your feedback. You can get in touch with us by filing issues, joining us in the #jquery-content IRC channel on freenode, or send an e-mail to content at jquery dot com.

Announcing the jQuery Plugin Registry

Posted on by

They say good things come to those who wait, and today we’re happy to end the waiting and unveil the jQuery Plugin Registry. We’ve worked long and hard to put together a brand new site that will serve to reduce the fragmentation and distribution problems that can be obstacles for plugin developers and consumers. We’ve also put an emphasis on remedying a number of the issues that plagued the old jQuery plugins site, especially with respect to workflows for contribution of both plugins and enhancements to the repository itself. The goal is to make sharing and browsing quality jQuery plugins a pleasant experience for everyone!

jQuery Plugin Registry: plugins.jquery.com
Source/Documentation/Issues: github.com/jquery/plugins.jquery.com

Downloading and Using Plugins

If you’re looking to just browse and use jQuery plugins in your application or site, not a lot has changed. Plugins each have basic pages that provide a link to the plugin download, as well as past versions, documentation, issue tracker, and source code repository. Download links may serve you a zip file with the plugin assets, or link to the best resource to download the build of the plugin you’re looking for.

Registering Your Plugin

Registering your plugin and having it listed on the site is not a complicated process; however, it assumes a number of aspects of the plugin development process, including using version control (git) and providing documentation on how to use it. You also have to include a plugin.jquery.json package manifest file, which provides all the information used to describe your plugin on the registry, including the version number, as well as the locations of the files and the documenation.

To register and publish your plugin, you’ll need to push your code to a public repository on GitHub, and add our post-recieve webhook URL (http://plugins.jquery.com/postreceive-hook) to your repository. The next time you push a semver tag, we’ll take care of registering the plugin name and updating its page on the site. When you’re ready to release the next version of your plugin, just tag and push again!

Users can download your plugin however you’d like them to. You can link directly to a JavaScript file for your users to save into their project, take advantage of the GitHub’s built-in zip file distribution, or even link to a custom build tool you may have online for further configuration.

That’s it — no uploading files to us, no wading through forms, and no manual updates for new versions.

(We plan to support other sites in the future! However, we’ve only been able to implement integration with GitHub at this point. If you’d like to assist with adding services, read on!)

Contributing to the Plugin Registry

Our work building the registry has informed and overlapped with a major initiative we’ve taken to open-source all of the content and design of all jQuery web sites. You’ve already seen part of this launch with the new api.jquery.com and jqueryui.com, and we’ll be talking more about this initiative later this week. As it relates to the Plugin Registry, it means that everything from the site documentation to the styles and templates to the post-receive hook itself is open source. So if you notice bugs or have ideas, you can raise and track issues and file your fixes as pull requests. You can even run a local instance of the site to iterate and test your changes.

Of course, if you’re a plugin author, you can also contribute by publishing your plugins to the registry. Even if you haven’t written plugins of your own, you can help out the authors of your favorite plugins by submitting pull requests that add a plugin.jquery.json manifest to their plugin’s repository.

Be Excellent To Each Other

We know this site has been long in the making, and we’re excited to finally be able to open it up for you to use, whether you’re looking for plugins to use in your app or you want to share your work with other developers. We’re looking forward to seeing lots of new plugins and old favorites make their way into the registry, so if you’re a plugin developer, we encourage you to get started as soon as you can with the registration process.

Name registration is on a first-come, first-served basis, and you can’t reserve a name prior to releasing a plugin. However, we recognize there is a huge ecosystem of jQuery plugins already out there, so especially in these early days of the registry’s existence, we do ask that authors reserve judgment and respect for other popular, widely-adopted plugins that may already have a reasonable historical claim to a particular name, even if it has not yet been registered. By and large, we hope that this will discourage “land grab” registrations, but we may step in to manually resolve a situation, should a particularly egregious case arise. “Squatting” on a plugin name is similarly disallowed, and may result in removal without warning!

(Translation: Ben Alman’s BBQ (Back Button & Query) plugin has long been a popular tool for working with the location.hash for navigation. Now is NOT a good time to create and register a sweet plugin for marking up quotations and call it the jQuery BBQ (<bold>,<blockquote>, & <q> plugin!)

That’s All, Folks

Thanks for your patience. Now go forth and publish! Should you encounter any trouble, please file issues, join us in the #jquery-content channel on freenode, or send an e-mail to plugins at jquery dot com

jQuery 1.9 final, jQuery 2.0 beta, Migrate final released

Posted on by

Are you sitting down? Well sit down, in front of your computer, and start downloading. We have several new jQuery releases for you to test. For your convenience, jQuery can even be downloaded while standing.

First up are the final versions of jQuery 1.9 and jQuery Migrate 1.0. We think these releases are pretty solid, because very few of you reported any problems in the beta versions. Just be sure to read the information in the jQuery 1.9 upgrade guide so that your transition will be smoother.

Next, take out your sunglasses. Today you get a glimpse at the future, and it’s bright. jQuery 2.0 is in beta test! We know it’s a lot to take in, so let’s recap the positioning for jQuery 1.9 and 2.0:

  • jQuery 1.9 and 2.0 have the same API. Several deprecated features such as $.browser have been removed from both versions. It’s all laid out in the jQuery 1.9 upgrade guide.
  • jQuery 1.9 runs on Internet Explorer 6, 7, and 8 (“oldIE”), just like previous versions. Consider it a cleaner, slimmer, modern-API upgrade from jQuery 1.8.
  • jQuery 2.0 will not run on oldIE. As a result of removing several layers of barnacle-encrusted code, it will be both faster and smaller than jQuery 1.9.
  • The team is supporting both jQuery 1.9 and 2.0 into the future. You choose which version you want to use based on your needs.

The jQuery Migrate plugin can be used with either 1.9 or 2.0 to detect deprecated and removed features, or to restore old features for those sticky situations where you need old code to run with new jQuery. The plugin and the messages it generates are documented in the project README.

If you’re on a recent version of jQuery core and have been avoiding deprecated features, these new jQuery releases may work for your code right out of the box. (Just remember, jQuery 2.0 doesn’t work on IE 6, 7, or 8!) Still, we recommend that you always start by including the jQuery Migrate plugin to see if it gives you any warnings.

The jQuery 1.9 final files are available on jQuery’s CDN, and should be available on the Google and Microsoft CDNs within a few days:

<script src="http://code.jquery.com/jquery-1.9.0.js"></script>
<script src="http://code.jquery.com/jquery-migrate-1.0.0.js"></script>

Or, for testing jQuery 2.0 beta 1, use the jQuery CDN:

<script src="http://code.jquery.com/jquery-2.0.0b1.js"></script>
<script src="http://code.jquery.com/jquery-migrate-1.0.0.js"></script>

For diagnostic purposes, you can also include the jQuery Migrate plugin with versions of jQuery all the way back to 1.6.4 to see what changes may cause issues with your code when you finally upgrade.

No matter which version of jQuery you use with the plugin, be sure to open the browser’s console to see what warnings or errors are being generated. Warnings given by the plugin start with the word “JQMIGRATE” and are listed in the plugin’s documentation. The description explains why the warning was given and how it can be fixed.

What’s New in 1.9

It may be a few weeks before the complete documentation for this release lands at api.jquery.com, especially since the API and other documentation sites are in the process of their own upgrade. For now, here’s a summary of what’s new and changed.

Streamlined API: Many deprecated and dubious features have been removed, as documented in the upgrade guide.

New .css() multi-property getter: Now you can pass .css() an array of CSS property names and it will return an object with the current values of all those CSS properties:

var dims = $("#box").css([ "width", "height", "backgroundColor" ]);
//  { width: "10px", height: "20px", backgroundColor: "#D00DAD" }

Enhanced cross-browser CSS3 support: jQuery 1.9 now supports the following CSS3 selectors across all browsers, all the way back to IE6: :nth-last-child, :nth-of-type, :nth-last-of-type, :first-of-type, :last-of-type, :only-of-type, :target, :root, and :lang.

New .finish() method: This method can be used to immediately complete all the animations queued on an element. The jQuery 1.9 RC1 blog post has more information and an example.

Source map support: You can now run the minified version of jQuery but use source maps for debugging. This can be extremely valuable for tracking down problems on a production web site. See the jQuery 1.9 RC1 blog post for a full description.

Many, many bug fixes: We’re especially proud of what we hope will be the final set of fixes for obscure issues in IE 6, 7, and 8. See the changelog below for a complete inventory.

Getting started with 2.0

Since jQuery 2.0 has its foundation in the work for jQuery 1.9, all the discussion in the upgrade guide also applies to 2.0. The Migrate plugin will identify many of these issues for you automatically.

If you’re using jQuery in non-web-site HTML situations such as an Android, iOS, or Windows 8 app, or a Chrome/Firefox add-on, jQuery 2.0 is an awesome choice. You can even use jQuery 2.0 on web sites if you don’t support oldIE or don’t mind using conditional comments:

<!--[if lt IE 9]>
    <script src="jquery-1.9.0.js"></script>
<![endif]-->
<!--[if gte IE 9]><!-->
    <script src="jquery-2.0.0.js"></script>
<!--[endif]-->

With this first beta of jQuery 2.0 we’ve made a huge down payment on major cleanup, cutting the size of the library by more than 10 percent. But we’re nowhere near done. There is more refactoring possible now that we can consistently depend on modern JavaScript, CSS, HTML, and DOM features being there. We’ll continue to tighten and clean up the code before 2.0 ships, and extend our work to make more functionality optional to shrink the size of custom builds.

They Built This For You

Many thanks to the people who have contributed to these two releases since 1.8.3 was shipped: Akintayo Akinwunmi, Alexander Farkas, Allen J Schmidt Jr, Ben Truyman, Bennett Sorbo, Callum Macrae, Carl Danley, Corey Frang, Daniel Gálvez, Dan Morgan, David Bonner, David Fox, Devin Cooper, Elijah Manor, Erick Ruiz de Chavez, Greg Lavallee, Ismail Khair, James Huston, Jay Merrifield, Jonathan Sampson, Julian Aubourg, Marcel Greter, Matt Farmer, Matthias Jäggli, Mike Petrovich, Mike Sherov, Oleg Gaidarenko, Paul Ramos, Richard Gibson, Rick Waldron, Rod Vagg, Roland Eckl, Sai Wong, Scott González, Sebi Burkhard, Timmy Willison, Timo Tijhof, Tom Fuertes, Toyama Nao, and Yi Ming He. Good work guys!

jQuery 1.9.0 final and 2.0.0 beta Changelog

Any tickets listed here that are not related to IE 6/7/8 support are also in the jQuery 2.0 beta.

Ajax

Attributes

Build

Core

Css

Data

Deferred

Effects

Event

Manipulation

Misc

Offset

Selector

Support

Traversing