A jQuery plugin to make your form controls look how you want them to. Now with HTML-5 attributes!
Works well with jQuery 1.6+, but we've received patches and heard that this works with jQuery 1.3.
Packaging of Uniform comes with source SASS files and minified CSS files, ready for consumption in live/production environment. You can install Uniform via one of two methods listed below:
npm install --save jquery.uniform
To create minified file, run (though this isn't necessary, as the minified file is already included in the package):
npm run build
Minified source file will be built inside
bower install --save jquery.uniform
Un-minified CSS files
For your own development purposes, to get human-readable, un-minified CSS outputs, you will need to install Uniform via NPM (as shown above), install the necessary dependencies through
npm install and then run
gulp. Doing so will recreate readable CSS files in
dist/css folder. Invoking
gulp --production however, will recreate minified CSS files (which is default behavior, what we already have in the
There are two ways to go with this:
Basically, you can use the final assets provided in
dist folder out of the box.
<header> of your markup (the latter, coming after jQuery):
Or if you are using our bundled version -
jquery.uniform.bundled.js file - which already comes with jQuery (beware not to include jQuery twice):
To have more control over your web assets, you can directly work with our SCSS and JS files, by importing them into or bundling with your own assets. Please be advised that our Gulp configuration (via Laravel-Elixir package) includes Auto-prefixer, i.e. browser prefixes are automatically added to CSS during the post-processing of SCSS files. Whatever your post-processing solution will be (Gulp-based or Compass), you need to make sure to include Auto-prefixer in that workflow. Our SCSS source files do not include browser prefixes out of the box!
See our Wiki page for documentation.
It sure would be handy if you could create a test page to help illustrate bugs. When you use the GitHub Issue Tracker, you could clone this bug template gist or use this jsfiddle to help illustrate your point.
Even if you don't do that, all sorts of feedback is welcome, but narrowing down your problem or providing an example would immediately help narrow down the problem quickly.