Apparently StringScanner#peek() isn't multibyte safe. WTF?
We're up to date with the 2014-02-20 CR.
Add 2.1.3 and ruby-head to Travis test targets.
Teensy tiny speed and memory usage improvements.
Merge commit '3b70a09f553fd40f8a63a3514fb3f40ce45d59e1' as 'test/css-parsing-tests'
Squashed 'test/css-parsing-tests/' content from commit 5afe94a

git-subtree-dir: test/css-parsing-tests
git-subtree-split: 5afe94a8adbd6716eedb6b374d70995060f0664a
Add a Rake task to pull in the latest upstream CSS tests.
Bring the parser and tokenizer up to date with the 5 September 2014 editor's draft spec.

Fixes several edge cases and incorporates various tokenization and parsing
changes in the spec.

The most significant outwardly visible change is that quoted URLs like `url("foo")`
are now returned as `:function` tokens and not `:url` tokens due a change in the
tokenization spec.
Don't omit the trailing semicolon when serializing a `@charset` rule.
Run upstream CSS parsing tests unmodified and remove redundant custom tests.

This'll make adapting to new spec/test changes much easier.
Patch CSS parsing tests to reflect spec changes to how quoted URLs are parsed.

Upstream pull request is here:
https://github.com/SimonSapin/css-parsing-tests/pull/5
Add a few serialization tests.
Bump the version to a dev version and update the readme.
Fix a doc comment.
Squashed 'test/css-parsing-tests/' changes from 5afe94a..86d34b7

86d34b7 Merge pull request #5 from rgrove/url-functions
cdda691 Make bad URL function tests more useful.
b89d403 Quoted URLs are now tokenized as functions.

git-subtree-dir: test/css-parsing-tests
git-subtree-split: 86d34b729978df74bc91a66ce0e2951187a1005c
Merge commit '683754e33ec57f8c6d944643cc021408e0fd064d' into dev-1.0.0

Conflicts:
	test/css-parsing-tests/component_value_list.json
Release 1.0.0.
Update status badges.