Use local ribbon image.
Remove unused local variables.

http://code.google.com/p/esprima/issues/detail?id=311
New example: syntax validator.

http://code.google.com/p/esprima/issues/detail?id=314
Split the unit tests fixture and runner.

http://code.google.com/p/esprima/issues/detail?id=307
Fix UMD pattern when loading with V8 shell.

http://code.google.com/p/esprima/issues/detail?id=291
Add defaults, rest, generator, expression field to Function interface

http://code.google.com/p/esprima/issues/detail?id=315
Ensure the coverage script understand the recent test runner split.

http://code.google.com/p/esprima/issues/detail?id=307
Update the coverage analysis result.

http://code.google.com/p/esprima/issues/detail?id=238
Update TravisCI node.js versions

http://code.google.com/p/esprima/issues/detail?id=317
Reject unterminated RegExp

http://code.google.com/p/esprima/issues/detail?id=318
Doc: Update the coverage check procedure.

http://code.google.com/p/esprima/issues/detail?id=307
Highlight focused nodes in the editor of parser demo.

If the line and column-based location info is enabled, the editor will
highlight the corresponding character range of the focused node in tree
widget.

http://code.google.com/p/esprima/issues/detail?id=319
Fix incorrect range of expressions inside parentheses

The character range of expressions in parentheses have included
the parentheses as well.

An example: "(42)"
Incorrect range of literal:   [0,4]
The correct range of literal: [1,3]

Furthermore in case of MemberExpression and CallExpression the
range have included the closing parenthesis but not the opening.
The commit fixes that as well.

An example: "(f())"
Incorrect range of call expression:   [1,5]
The correct range of call expression: [1,4]

13 tests have been updateded to expect the correct range.

http://code.google.com/p/esprima/issues/detail?id=309
Represent holes in ArrayExpression as null

http://code.google.com/p/esprima/issues/detail?id=321
API change for TryStatement

http://code.google.com/p/esprima/issues/detail?id=245
Update to Benchmark.js 1.0.0.

It is now at version 1.0.0 (revision e9667c4ee9, Aug 16 2012).

http://code.google.com/p/esprima/issues/detail?id=323
Clean-up and refactor speed comparison code.

Mostly align the code to fit the benchmark suite test code.
Also, generate the HTML result instead of static hard-coded table.

http://code.google.com/p/esprima/issues/detail?id=325
Update to Escodegen 0.0.6 and add string quotes rewrite option.

Now using Escodegen revision 2e88a31f5d (Aug 28, 2012).

http://code.google.com/p/esprima/issues/detail?id=326
Mention the new Esmangle project.
Clarify the speed comparison situation.