Ensure Graph creates a copy of the x/yScale before modifying it
Removed trailing comma in example
Support empty first series in stack
This can easily happen when series of different length are drawn and the RangeSlider is used to restrict the graph to a range where one of the series is empty.
Fine tuning for the detail dot
Jquery noconflict fix (bug fixes for #396)
To make it actually compile again.
In mbostock/d3 issue #1016, the scope of the `tick` class on a svg y-axis element changed to include the entire g object (line and text), not just the line. The Rickshaw CSS for `.y_ticks .tick` was created in the early commits, and sets the style to be a 2px width semitransparent stroke. Due to the change in scoping of the style class, the stroke element applies to both the line and the text element, creating a shadow on the y-axis text labels. By changing the scope of the stroke stanza from `.y_ticks .tick` to `.y_ticks .tick line`, the stroke now applies only to the line, and not to the text element, this removing the stroke shadow on the text label.
x/yScale is coming from the configuration dictionary which may be referenced by the Graph creator, or shared with other Graphs. We need to ensure we copy the scale so that our mutations do not change the object given to us.
Rickshaw.Graph.RangeSlider.Preview supports millisecond zooming
…l_sub_renderers_domain Fix #377: Ensure multi renderer consults it's sub renderers about how th...
… they perceive their domain
Changed the domainScale interpolate function to d3.interpolateNumber (vs. d3.interpolateRound) so that the RangeSlider Preview Window could zoom into millisecond levels of precision (before it would only allow a window of 1 second)
…s for range slider previews; closes #364