add formenctype test
Add test for ES6 Promises
Add test for `CSS.escape()`
Merge pull request #1172 from mathiasbynens/CSS.escape

Add test for `CSS.escape()`
Merge pull request #1169 from kristerkari/master

Add test for ES6 Promises
Merge pull request #1157 from patrickkettner/formenctype

add formenctype test
add literal period to history's blacklist, ensuring that its android 2 and not android 22
Merge pull request #1175 from patrickkettner/twonottwenty

add literal period to history's blacklist, ensuring that its android 2 and not android 22
add note about the silk browser having a false positive on box-shadow
Merge pull request #1176 from patrickkettner/silkissue

add note about the silk browser having a false positive on box-shadow
Merge pull request #1173 from robwierzbowski/rw/grunt-improvements

Grunt improvements
Improve/standardize/modernize Gruntfile

1. Standardize formatting of arrays and objects
    - Fixes formatting inconsistencies in the Gruntfile. Now arrays and objects
    are:
    single_space: after_colon,
    One value: [single_line],
    Multiple values: [
      multiple,
      lines
    ]

2. Move grunt-cli to a peer dependency, document installation in README
    - The current recommendation is to install grunt-cli globally (from Grunt and
    Grunt based projects like Yeoman).
    - The modernizr.build() method was specifying a path to the local grunt cli
    excutable. Switched to the generic grunt command, since cli should be installed
    globally.

3. Use load-grunt-tasks to... load grunt tasks!
    - Sindre wrote a nice plugin that is used widely in the Yeoman and Grunt
    communities to load tasks in a cleaner fashion than matchdep.
    - Moves loading tasks to the top near our other require statements.
    - Since we're asking users to run `npm install` there should be no need to check
    if a package is installed or not. If the project is installed as a dependency
    all of the required packages will be installed as well.

4. Fix config-all.json formatting
    - Running `grunt test` reformats the config-all file, leaving your working
    directory dirty. Committing the reformatted file so that running a test task
    doesn't impact the repo at all :).

5. Move jshint before build
    - It's convention to jshint source files before you build, so that if there are
    glaring jshint errors your build won't complete.

6. Rename clean targets to be more descriptive

7. Revise the readme to ask people to run all tests (jshint, qunit, and nodeunit)
Undo over-agressive linebreaks
Remove unused lib/generate-init.js

Looks like the last reference to this file was removed in 2012 in
ff031ef330962e0639776b852db8809ea81907c8
Minor cleanup of src/generate.js

- Minor cleanup and comments
- We're using node/v8 so we can use native forEach
Remove unused lib/app.build.js

The only two references to it are the initial commit
541af0bd473ffe154557b5f978ad25c2b1c4c38

this moving of the file:
16ad49aa670fa1207f873beb0069c5575be77485

and this cleanup that says "I don't know what this file is for":
2906bc78cf765e7b91fc00dc5de109265aa50d09
Move sauce-browsers.json to test/

It's used only by tests, so put it in test.
Move src/generate.js to lib/generate-init.js

Generate is not actualy part of the modernizr source, but part of the build
system. The code it generates is part of the source. Adding -init to follow the
same pattern as generator-meta, and because it's more descriptive.
Switch generate-init to node-style module

Keeping build code node-style, and Modernizr output code require-style.
WIP