The official jQuery user interface library.
Go to file
Michał Gołębiowski-Owczarek 600057f59c
Demos: Make autocomplete demos work on jqueryui.com
The `jqueryui.com` demos build process deAMDifies HTML files, replacing required
JS files with direct script tags. On the other hand, when running demos locally
from the jQuery UI repository, RequireJS is used.

This used to work fine until we got a new `search.js` file introduced in
gh-2187. The deAMDifying process doesn't touch non-HTML files which made loading
autocomplete demos crash on "require is not a function"

To resolve the issues without a major rearchitecture of the build process,
the `search.js` file now detects AMD and uses `require`, falling back to relying
on the `jQuery` global in the other case.

Closes gh-2274
Ref gh-2187
Ref jquery/jqueryui.com#216
2024-07-30 08:31:10 +02:00
.github Build: Group dependabot PRs updating GitHub Actions 2024-07-08 19:04:44 +02:00
build Release: Update download.jqueryui.com from 2.3.6 to 2.3.7 2024-07-05 18:53:40 +02:00
demos Demos: Make autocomplete demos work on jqueryui.com 2024-07-30 08:31:10 +02:00
external All: Drop support for jQueries different than the latest for each major 2024-05-15 00:38:30 +02:00
tests Dialog: Add aria-modal support 2024-06-14 13:04:00 +02:00
themes/base All: Drop support for IE & some other browsers (but mostly IE) 2024-05-15 00:38:40 +02:00
ui Dialog: Add aria-modal support 2024-06-14 13:04:00 +02:00
.csslintrc Build: Update to the latest version of Grunt & many other packages 2020-10-14 23:55:35 +02:00
.editorconfig Tests: replace grunt-contrib-qunit with jQuery test runner 2024-03-29 09:13:46 -04:00
.eslintignore Build: Fork vendors to remove QUnit deprecated API usage 2023-05-10 10:53:57 +02:00
.eslintrc.json Build: Migrate from JSHint & JSCS to ESLint 2021-06-07 00:58:12 +02:00
.gitattributes Build: Force LF for JS source files 2014-03-05 10:15:37 +01:00
.gitignore Tests: align test runner with other repos 2024-04-09 13:31:27 -04:00
.mailmap Build: Add Felix to .mailmap, update AUTHORS.txt 2022-01-15 01:26:00 +01:00
.npmignore Build: Add /.github, /build & /external to .gitignore 2024-05-15 14:18:07 +02:00
.npmrc Tests: replace grunt-contrib-qunit with jQuery test runner 2024-03-29 09:13:46 -04:00
AUTHORS.txt Build: Update AUTHORS.txt 2024-06-14 18:53:54 +02:00
bower.json Core: Update compatible jQuery versions 2024-05-15 18:13:35 +02:00
CONTRIBUTING.md Docs: Fix the link to Mongoose 2024-05-15 00:38:40 +02:00
Gruntfile.js Build: Report compressed sizes in compare_size 2024-05-20 18:59:58 +02:00
LICENSE.txt All: Update JS Foundation mentions to OpenJS Foundation 2022-07-19 09:36:55 +02:00
package.json Tests: remove code supporting jenkins and testswarm 2024-05-15 15:19:23 -04:00
README.md Docs: Change a few most common domains from HTTP to HTTPS 2024-04-26 16:25:34 +02:00
SECURITY.md Docs: Add a security policy in SECURITY.md 2022-07-19 20:59:15 +02:00

jQuery UI - Interactions and Widgets for the web

Note: jQuery UI is in maintenance-only mode. Please read the project status blog post for more information.

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 jqueryui.com to get started, jqueryui.com/demos/ for demos, api.jqueryui.com for API documentation, or the Using jQuery UI Forum for discussions and questions.

If you want to report a bug/issue, please visit the GitHub issues page. Archive of older bug reports is kept for historical reasons in read-only mode at bugs.jqueryui.com. If any of them still matters to you, please open a bug about it on GitHub, linking to the legacy bugs.jqueryui.com issue for context.

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 irc.freenode.net.

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.

For more information, see the contributing page.

Running the Unit Tests

Run the unit tests manually with appropriate browsers and any local web server. See our environment setup and information on running tests.

You can also run the unit tests npm run test:unit -- --help.