Skip to content
This repository

A fork of jQuery UI to push development of some plug-ins. A updated version of Selectmenu (originally by filament group) and a accessible version of jQuery UI Tabs. See branches!

This branch is 595 commits ahead and 617 commits behind selectmenu

Octocat-spinner-32 build Updating jQuery to 1.10.2. July 05, 2013
Octocat-spinner-32 demos Demos/tests: Losslessly recompress PNG/GIF images. August 26, 2013
Octocat-spinner-32 external Updating Globalize to v0.0.1. July 11, 2013
Octocat-spinner-32 tests Demos/tests: Losslessly recompress PNG/GIF images. August 26, 2013
Octocat-spinner-32 themes CSS Framework: Display child links within .ui-state-hover and .ui-sta… August 07, 2013
Octocat-spinner-32 ui Draggable: Safe activeElement access from iFrames for IE9, prevent wi… August 28, 2013
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 Update .gitattributes to only touch files with text content. January 08, 2013
Octocat-spinner-32 .gitignore Remove environment-specific files from .gitignore. May 09, 2013
Octocat-spinner-32 .jshintrc Updated .jshintrc settings. April 08, 2013
Octocat-spinner-32 .mailmap Mailmap: Fix Nick Pierpoint. August 06, 2013
Octocat-spinner-32 .travis.yml Build: Add support for running on Travis June 12, 2013
Octocat-spinner-32 AUTHORS.txt Update AUTHORS.txt. September 02, 2013
Octocat-spinner-32 Added December 12, 2012
Octocat-spinner-32 Gruntfile.js Build: Implement an asciilint task to verify content of ui files (ign… July 03, 2013
Octocat-spinner-32 MIT-LICENSE.txt Update copyright year to 2013. January 10, 2013
Octocat-spinner-32 README: Updated build instructions. August 27, 2013
Octocat-spinner-32 jquery-1.10.2.js Updating jQuery to 1.10.2. July 05, 2013
Octocat-spinner-32 package.json Upgrade grunt-contrib-jshint to 0.6.3. August 28, 2013

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 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 build task
grunt build

# 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.