Fix for Issue 421: Range selector disappear after resize
Namespace the canvas proxy in auto tests.
Fix documentation for underlayCallback (Issue 379)
Merge pull request #204 from sauter-hq/55eb8485b406174f15dcee0e97abc4c466de7733

Added support for stepPlot per-series
Merge pull request #208 from paulfelix/master

Fix for Issue 421: Range selector disappear after resize
add a (non-breaking) space between series name and value in the legend (Issue 307)
Fix tests to handle the new space in the legend
Add CSS "reset" to fix Issue 429
Slightly scary change to fix issue 426
Call zoomCallback from touch interactions (issue 395)
support "double-tap" to zoom out on touch devices
Add methods to DygraphOps to dispatch mouseover and mouseout; some simplification and clean-up.
Fix bug 428, add test which catches exception. What an annoying little bug.
Merge pull request #209 from kberg/i428

Fix bug 428
Fix Issue 181: labelsDiv flashes when the mouse hovers over it.
Merge branch 'master' of github.com:danvk/dygraphs
Fix Issue 347: three-finger zoom crashes the display on iOS
Fix part 1 of Issue 256: Annotations attachAtBottom Property
Add new options xRangePad and yRangePad

These options provide a fixed margin (in pixels) around the
user-specified or autoselected axis range to ensure all data points are
fully visible. If these are not set by the user, behavior reverts to
backward compatible mode.

This helps avoid the issue of data points drawn at the graph edges not
being properly visible.  For example, in a 100-pixel high plot area, a Y
coordinate of zero on a graph with yrange [0, ...] will be scaled to
domY=100 which is outside the 0..99 visible area.

If I'm understanding it right, the original padding algorithm works
as follows:

  Add 10% padding for automatic Y ranges, but not for user-supplied
  ranges, and move a close-to-zero edge to zero except if avoidMinZero
  is set. If logscale is set, add a variable amount of padding at the
  top but none at the bottom.

This is not very intuitive, and lines drawn at the edge of a
user-supplied range will still be invisible.

The new algorithm consistently ensures that there are at least
{x,y}RangePad pixels available for drawing outside of the data range,
both for user-specified and autoselected ranges.

Setting a small xRangePad combines nicely with drawAxesAtZero,
it will provide tick marks next to the legend due to the grid extending
slightly past the axis.

See the included gallery demo 'Edge Padding'. The default setting
corresponds to legacy behavior. Recommended settings:
  includeZero: true,
  drawAxesAtZero: true,
  xRangePad: 4,
  yRangePad: 10
Fix the other half of Issue 256 (annotation stacking)