ComponentGroup ordering now is intuitive - first thing in front. Fix #222
Update plottable.js, plottable.d.ts, and other build artefacts
Don't depend on clientWidth and clientHeight

clientWidth and clientHeight don't get intialized properly on top-level <svg>s
in Firefox (FF bug #874811). Instead, the top-level Component now reads the
width and height attributes from the svg. main.js has been added to properly
set these properties. In addition, Plottable.Utils now has a function
getSVGPixelWidth() that performs the same calculation. That call can be
added to Component.computeLayout() if necessary.
Main.js now uses utils method for getting width, drop coverage %

Lowering the coverage percentage in anticipation of architectural
restructuring and barnstorming.
Merge pull request #226 from palantir/fix-ghpages-FF

Don't depend on clientWidth and clientHeight
Use nulls instead of base Component for empty cells in Table

component.constructor.name didn't work on IE, so now instead of using base
Components to fill empty cells in Tables null is used. Null checks have been
added to the appropriate spots in Table.

In addition, getBoundingClientRect() wasn't returning the right result on
Firefox (it returned the correct upper-left corner, but the returned rectangle
had 0 width and 0 height), so the tick label cutoff calculation in Axis has
been changed to use availableWidth and availableHeight.

Also fixed tests that broke because of the change to nulls, and a few off-by-1
test errors on FF.
Update plottable.js, plottable.d.ts, and other build artefacts
Update plottable.js, plottable.d.ts, and other build artefacts
Remove commented-out line.
Merge pull request #227 from palantir/fix-ghpages-ie

Use nulls instead of base Component for empty cells in Table
Merge pull request #228 from palantir/master

Merge fixes for FF and IE into gh-pages.