jquery-ui-forms was designed to work with jQuery UI. The project currently depends on the following libraries:
kendo-ui-forms has not been tested against any other versions of these libraries. You may find that versions other than these are compatible with kendo-ui-forms, but we make no claims to support those version, nor can we troubleshoot issues that arise when using those versions.
This repository contains both the full and minified builds of the library in the dist folder
A working sample of the plugin can be found in the samples directory
Once you clone the repo, run
npm install
to grab all of the essential dependencies for dev, build and test. The repo uses grunt for all of these, so run
grunt
to make sure everything is working. If you see text indicating that the jshint, concat and uglify tasks have run without errors, you’re golden!
The table below contains a list of HTML5 Form elements available in jQuery UI, and which can be used to polyfill inputs.
Feature | jQuery UI Equivalent? |
---|---|
Color |
No |
Number |
Yes |
Range |
Yes |
File |
No |
DateTime |
No |
DateTime-Local |
No |
Time |
No |
Month |
Yes |
Week |
Yes |
Date |
Yes |
Buttons |
Yes |
Progress |
Yes |
Meter |
Yes |
Datalist |
Yes |
Search |
No |
Autocomplete |
Yes |
Validation |
Yes |
Tests are written in jasmine and can be found in the spec/ directory. To run the tests from the command-line, call
grunt test
The Kendo UI Forms Project also uses Karma to ensure cross-browser coverage of all tests. Browsers tested include:
-
Google Chrome
-
Google Chrome Canary
-
Firefox
-
Opera
-
Safari [OSX Only]
-
IE [Windows Only]
If you don’t have any of these browsers, Karma will fail. But hey, this is cross-browser polyfill development here, so just install them all!
To run Karma, you can call
grunt x-test
and Karma will take care of launching each browser, running the specs and shutting them down again (except for Safari, for some reason, so that’s awesome).
If you want to run the jasmine tests in your browser, as opposed to running the multi-browser tests or from the console every time, you can spin up a local webserver and navigate to spec/runner.html, or navigate directly via the filesystem
file://localhost/[path]/jquery-ui-forms/spec/runner.html
If you’re using Chrome and taking the latter approach, some of the tests will fail because of cross-domain features in Chrome. To work around this, run Chrome with the --allow-file-access-from-files terminal command.
For OSX:
open -a /Applications/Google\ Chrome.app --args --allow-file-access-from-files
And Windows:
C:\Users\[UserName]\AppData\Local\Google\Chrome[ SxS]\Application\chrome.exe --allow-file-access-from-files
For change logs and release notes, see the changelog file.