Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

The official jQuery user interface library.

Octocat-spinner-32 build Build: Migrate to jquery-release April 24, 2014
Octocat-spinner-32 demos Dialog demo: Update modal form demo April 24, 2014
Octocat-spinner-32 external External: Update mousewheel plugin, copy only main file April 14, 2014
Octocat-spinner-32 tests Selectmenu: Work around test bug in IE April 24, 2014
Octocat-spinner-32 themes All: Updating copyright year to 2014 January 28, 2014
Octocat-spinner-32 ui Selectmenu: Default disabled option to null April 21, 2014
Octocat-spinner-32 .csslintrc Use .csslintrc instead of inlining rules in the Gruntfile. March 15, 2013
Octocat-spinner-32 .editorconfig Exempt external directory from .editorconfig rules October 21, 2012
Octocat-spinner-32 .gitattributes Build: Force LF for JS source files March 05, 2014
Octocat-spinner-32 .gitignore Build: Update grunt-compare-size to latest, add it's .sizecache.json … September 20, 2013
Octocat-spinner-32 .jscs.json Build: Update grunt and grunt-jscs-checker, use jquery preset for jscs January 10, 2014
Octocat-spinner-32 .jshintrc Updated .jshintrc settings. April 08, 2013
Octocat-spinner-32 .mailmap Updated author information. December 10, 2013
Octocat-spinner-32 .travis.yml Build: Add support for running on Travis June 12, 2013
Octocat-spinner-32 AUTHORS.txt Authors: Update February 11, 2014
Octocat-spinner-32 Docs: Reduce contributing guidelines by linking to January 09, 2014
Octocat-spinner-32 Gruntfile.js External: Update mousewheel plugin, copy only main file April 14, 2014
Octocat-spinner-32 MIT-LICENSE.txt All: Updating copyright year to 2014 January 28, 2014
Octocat-spinner-32 README: Update build instructions to use concat tasks (instead of build) November 26, 2013
Octocat-spinner-32 bower.json External: Update mousewheel plugin, copy only main file April 14, 2014
Octocat-spinner-32 jquery.js All: Rename jquery.js to exclude version in filename March 05, 2014
Octocat-spinner-32 package.json Build: Add Felix Nagel as a maintainer April 24, 2014

jQuery UI - Interactions and Widgets for the web

jQuery UI is a curated set of user interface interactions, effects, widgets, and themes built on top of jQuery. Whether you're building highly interactive web applications, or you just need to add a date picker to a form control, jQuery UI is the perfect choice.

If you want to use jQuery UI, go to to get started, for demos, for API documentation, or the Using jQuery UI Forum for discussions and questions.

If you want to report a bug/issue, please visit

If you are interested in helping develop jQuery UI, you are in the right place. To discuss development with team members and the community, visit the Developing jQuery UI Forum or #jqueryui-dev on

For contributors

If you want to help and provide a patch for a bugfix or new feature, please take a few minutes and look at our Getting Involved guide. In particular check out the Coding standards and Commit Message Style Guide.

In general, fork the project, create a branch for a specific change and send a pull request for that branch. Don't mix unrelated changes. You can use the commit message as the description for the pull request.

Running the Unit Tests

Run the unit tests with a local server that supports PHP. No database is required. Pre-configured php local servers are available for Windows and Mac. Here are some options:

Building jQuery UI

jQuery UI uses the Grunt build system.

To build jQuery UI, you must have node.js installed and then run the following commands:

# Install the Grunt CLI
npm install -g grunt-cli

# Clone the jQuery UI git repo
git clone git://
cd jquery-ui

# Install the node module dependencies
npm install

# Run the concat task to concatenate files
grunt concat

# There are many other tasks that can be run through Grunt.
# For a list of all tasks:
grunt --help

For committers

When looking at pull requests, first check for proper commit messages.

Do not merge pull requests directly through GitHub's interface. Most pull requests are a single commit; cherry-picking will avoid creating a merge commit. It's also common for contributors to make minor fixes in an additional one or two commits. These should be squashed before landing in master.

Make sure the author has a valid name and email address associated with the commit.

Fetch the remote first:

git fetch [their-fork.git] [their-branch]

Then cherry-pick the commit(s):

git cherry-pick [sha-of-commit]

If you need to edit the commit message:

git cherry-pick -e [sha-of-commit]

If you need to edit the changes:

git cherry-pick -n [sha-of-commit]
# make changes
git commit --author="[author-name-and-email]"

If it should go to the stable branch, cherry-pick it to stable:

git checkout 1-10-stable
git cherry-pick -x [sha-of-commit-from-master]

NOTE: Do not cherry-pick into 1-10-stable until you have pushed the commit from master upstream.

Something went wrong with that request. Please try again.