Skip to content
This repository
branch: master

Apr 14, 2014

  1. Mike Bostock

    Merge branch '3.4.6'

    authored April 13, 2014
  2. Mike Bostock

    Merge branch 'mean' into 3.4.6

    authored April 13, 2014
  3. Mike Bostock

    Merge branch 'fix-parse-timezone' into 3.4.6

    authored April 13, 2014
  4. Mike Bostock

    Merge branch 'fix-quantile-null' into 3.4.6

    authored April 13, 2014

Apr 11, 2014

  1. Jason Davies

    Optimise d3.mean.

    Originally we were using Welford’s algorithm, but this is primarily
    useful when computing the variance in a numerically stable manner, since
    Welford’s approach requires an incremental mean.
    I’ve removed a test for the mean of more than one instance of
    Number.MAX_VALUE as this is unlikely to occur in practice; most likely
    this was the reason I used Welford’s algorithm in the first place.
    There’s a paper [1] comparing various algorithms for computing the mean,
    and Welford’s is actually slightly less accurate than the naïve
    approach.  There are some more accurate approaches but I think it’s
    overkill for d3.mean.
    [1] Youngs, Edward A., and Elliot M. Cramer. "Some results relevant to
    choice of sum and sum-of-product algorithms." Technometrics 13.3 (1971):
    Related: #1842.
    authored April 11, 2014

Apr 10, 2014

  1. Mike Bostock

    Fix #1839 - sign of parsed timezone offset.

    authored April 10, 2014
  2. Jason Davies

    Code formatting: fix indent.

    authored April 10, 2014

Apr 08, 2014

  1. Mike Bostock

    The quantile scale should ignore null, too.

    authored April 08, 2014
  2. Mike Bostock

    Merge branch '3.4.5'

    authored April 07, 2014
  3. Mike Bostock

    Merge remote-tracking branch 'origin/geo-empty-polygon' into 3.4.5

    authored April 07, 2014

Apr 06, 2014

  1. Mike Bostock

    Run each benchmark separately.

    authored April 05, 2014
  2. Mike Bostock

    Add d3.interpolateString benchmark.

    authored April 05, 2014
  3. Mike Bostock

    Only coalesce exact string matches.

    If there are a lot of matching numbers, it’s faster to do direct string equality
    comparisons than it is to coerce to a number and compare numerically.
    authored April 05, 2014
  4. Mike Bostock

    Optimize interpolateString.

    authored April 05, 2014

Apr 04, 2014

  1. Jason Davies

    Don’t generate empty polygons during clipping.

    Fixes #1823; spurious closePath events were being generated for
    degenerate polygons due to generation of empty polygons and rings in
    rare cases.
    authored April 04, 2014

Mar 25, 2014

  1. Mike Bostock

    Merge branch '3.4.4'

    authored March 24, 2014

Mar 24, 2014

  1. Mike Bostock

    Test for interpolate to null.

    I’m not entirely sure this is the most useful behavior, but since typeof null is
    "object" and +null is 0, interpolating to null is equivalent to interpolating to
    the number zero.
    authored March 24, 2014
  2. Mike Bostock

    Save a few bytes.

    authored March 23, 2014
  3. Mike Bostock

    Preserve tick ordering when updating axis.

    Fixes #1748.
    authored March 23, 2014
  4. Mike Bostock

    Getter support for transition.{delay,duration}.

    Fixes #1773.
    authored March 23, 2014
  5. Mike Bostock

    Default to suitable precision.

    The point of this method is to pick the right precision for you!
    authored March 23, 2014
  6. Mike Bostock

    More standard precision interpretation.

    Rather than overload the meaning of precision to bias the selection of the SI
    prefix, always use the standard SI prefix, and use the precision in the same
    sense as with fixed digits: the number of digits after the decimal point.
    authored March 23, 2014
  7. Mike Bostock

    Consistent SI-prefix for small numbers.

    For reasons that I can’t recall, the SI-prefix behavior was different for small
    numbers (between -1 and 1) than it was for large numbers. This commit enforces
    consistent behavior, so that the coefficient is always in the range [1, 1000),
    like in engineering notation.
    For example, the old d3.format("s") would display 0.01 as "0.01", whereas the
    new behavior displays it as "10m".
    authored March 23, 2014
  8. Mike Bostock

    Consistent SI-prefix for ticks. Fixes #1746.

    When a SI-prefix format (type "s") is passed to scale.tickFormat, compute a
    suitable SI-prefix based on the maximum value in the range, and then use that
    prefix for all ticks rather than computing the SI-prefix on a per-tick basis.
    authored March 23, 2014
  9. Mike Bostock

    Fix ordinal scales with singleton domains.

    Fixes #1717. Turns out, -1 % 1 is 0!
    authored March 23, 2014
  10. Mike Bostock

    Listen to the touch target.

    This ensures that if the touch target is removed from the DOM during a zoom
    gesture, the zoom behavior continues to receive events; touch events, unlike
    other events, are always dispatched to the target of the touchstart event rather than the window.
    authored March 23, 2014
  11. Mike Bostock

    Better ticks for subsecond domains.

    Rather than starting the ticks on the minimum domain value, round up based on
    the step size. Fixes #1757.
    authored February 27, 2014
  12. Darrick Brown

    100% to 125% faster #rgb/#rrggbb string parsing across all platforms.…

    authored February 04, 2014 mbostock committed March 23, 2014
  13. Timmy Willison

    Shorten selectAll to just `Sizzle`

    authored July 09, 2013 mbostock committed March 23, 2014
  14. Timmy Willison

    Remove redundant Sizzle.uniqueSort call

    authored July 09, 2013 mbostock committed March 23, 2014
  15. Mike Bostock

    Clamp latitude for conic conformal projection.

    The Lambert conic conformal projection extends to infinity along the outer edge
    of the projection, and thus the latitude must be clamped either at -π/2 or +π/2
    depending on the parallels. Fixes #1802.
    authored March 22, 2014
  16. Mike Bostock

    Remove workaround for WebKit bug 44083.

    This was fixed in 2010, so I think it’s safe to remove the workaround now.
    authored March 20, 2014
  17. Mike Bostock

    d3.touch defaults to changedTouches.

    This way, it’s easier to tell whether the touch changed during the event. This
    also fixes #1600 because the drag behavior now only dispatches a drag event on
    elements that moved, even if multiple touches are active.
    authored March 19, 2014
  18. Mike Bostock

    Add d3.touch; fix #1786.

    The drag behavior no longer crashes when the element being dragged is removed
    from the DOM. In addition, the new d3.touch method extracts a single identified
    touch from the current touch event, making it more efficient during multitouch.
    The drag behavior now assigns touchmove and touchend listeners on the target
    element of the touchstart event, rather than the window.
    authored March 19, 2014
  19. Mike Bostock

    Fix all touches ending on any touch ending.

    The drag behavior registers a touchend listener for each started touch; however,
    a touchend event is dispatched to ALL listeners when any touch ends, not just
    for the corresponding starting touch. The drag behavior must therefore detect
    whenever the ending touch is the corresponding starting touch, and ignore other
    ending touches.
    This fixes the drag behavior during multitouch, as discussed in #1786.
    authored March 19, 2014
Something went wrong with that request. Please try again.