Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Jul 4, 2015
  1. Merge branch '3.5.6'

    authored
Commits on Apr 4, 2015
  1. @jasondavies

    Fix for mousewheel interrupting zoom transition.

    jasondavies authored
    If a zoom transition is in progress, using zoom.event, a mousewheel
    gesture will interrupt the transition and cause a zoomend event, which
    resets the center0 variable to null.  Previously, the center0 variable
    was assigned in the mousewheel handler prior to the interruption.  This
    fix assigns it after the interruption.
Commits on Apr 1, 2015
  1. @jasondavies
Commits on Mar 24, 2015
  1. @jasondavies

    Fix combined mousewheel/drag gesture.

    jasondavies authored
    During a combined zoom/pan gesture, controlled via simultaneous use of
    the mousewheel and dragging, it is possible for the drag to finish
    before the use of the mousewheel finishes.  The mousewheel gesture is
    deemed to be finished if 50ms passes with no mousewheel event.
    
    Although the "zoomend" event is only dispatched when *both* gestures
    have finished, the variable "center0" was being reset when *either*
    gesture was finished, causing an error in the mousewheel handler.
    
    Fixes #2205.
Commits on Feb 10, 2015
  1. Fix d3.select(document) and d3.select(object).

    authored
    Also add tests for d3_documentElement and d3_window so that they work for the
    three cases we care about: a node, a document and a window. For anything else
    they return undefined.
Commits on Feb 7, 2015
  1. Merge branch '3.5.4'

    authored
  2. Make d3_window a bit more lenient.

    authored
    If the passed node is the window itself, return it.
  3. Merge pull request #2152 from mauromelis/patch-1

    authored
    Added it-IT locale
  4. @jasondavies

    Fix d3.select(window).

    jasondavies authored
    d3.select(window) calls d3_documentElement(window), which fails since
    window objects don’t have an ownerDocument property.  This fix falls
    back to using node.document if node.ownerDocument doesn’t exist.
  5. Demote JSDOM to development dependency; fix #2190.

    authored
    Code that previously assumed a global document or window now uses the related
    node’s ownerDocument or ownerDocument.defaultView as appropriate.
    
    If no related node is available, the corresponding code will crash; however, the
    rest of D3 will work just fine. For example, you can’t use d3.select(string)
    unless a global document is available; it just doesn’t make sense. Use
    d3.select(node) instead, followed by selection.select(string).
    
    Code that previously checked for a global on the window (e.g., XDomainRequest)
    now uses the global context (`this`) rather than the window.
Commits on Feb 6, 2015
  1. @wilg
Commits on Jan 28, 2015
  1. @vladh
Commits on Jan 15, 2015
  1. @arjenvanoostrum

    Update nl-NL.js

    arjenvanoostrum authored
    changed days and months to lowercase
Commits on Jan 14, 2015
  1. @arjenvanoostrum

    add Dutch locale

    arjenvanoostrum authored
Commits on Dec 31, 2014
  1. @tpreusse
Commits on Dec 30, 2014
  1. Fix selection.interrupt.

    authored
    Even if no further transitions are scheduled on the element, we must still
    advance the active counter to interrupt the active transition. Fixes #2165. Also
    added better tests that verify interruption.
Commits on Dec 22, 2014
  1. Use createElement if namespaceURI is undefined.

    authored
    Normally selection.append is only called on normal elements that have a defined
    namespaceURI. However, if createElement is called on a shadow root, then
    namespaceURI is null. Now we correctly fallback to createElement instead of
    createElementNS in this case. Fixes #2161.
Commits on Dec 11, 2014
  1. @mauromelis

    Added it-IT locale

    mauromelis authored
Commits on Dec 9, 2014
  1. Merge branch '3.5.2'

    authored
  2. Fix d3.transition(name).

    authored
Commits on Dec 8, 2014
  1. Merge branch '3.5.1'

    authored
  2. Better interruption semantics.

    authored
    When a transition is interrupted, the interrupt event is dispatched immediately
    (such as within a call to selection.interrupt). This is easier to understand and
    guarantees that the interrupt event on an interrupted transition is dispatched
    prior to the start event on an interrupting transition, fixing #2140.
    
    Calling selection.interrupt repeatedly no longer cancels any scheduled (but
    inactive) transitions, fixing #2141. Calling selection.interrupt when there is
    no active transition now has no effect.
    
    An interrupt event is only dispatched if the active transition is interrupted,
    and not if a scheduled transition was cancelled, as when a delayed transition is
    superceded by an earlier transition on the same element. These transitions are
    cancelled silently, fixing #2144.
    
    Lastly, transition event listeners now see the latest bound data, rather than
    using the data that was captured shortly after the transition was scheduled.
    Fixes #2142.
Commits on Dec 6, 2014
  1. Merge branch '3.5'

    authored
Commits on Dec 1, 2014
Something went wrong with that request. Please try again.