1. 05 May, 2016 5 commits
  2. 25 Apr, 2016 3 commits
  3. 20 Apr, 2016 3 commits
  4. 31 Mar, 2016 1 commit
  5. 18 Feb, 2016 2 commits
  6. 13 Feb, 2016 2 commits
  7. 11 Feb, 2016 3 commits
  8. 01 Feb, 2016 1 commit
  9. 27 Jan, 2016 1 commit
    • Mike Bostock's avatar
      Fix #2722 - case-sensitivity of selection.append. · 05fd32dd
      Mike Bostock authored
      If the implicit namespace of the created element matches that of the document
      element, the document’s createElement should be used instead of createElementNS.
      This way, in documents for which createElement is case-insensitive—most notably
      HTML documents—selection.append is likewise case-insensitive.
      05fd32dd
  10. 20 Jan, 2016 1 commit
  11. 11 Jan, 2016 2 commits
  12. 05 Jan, 2016 1 commit
    • Stef Walter's avatar
      Fix drag behavior on for <svg:use> elements · 17cc510c
      Stef Walter authored
      Drag behavior is broken for <svg:use> elements on certain
      browsers. This includes d3.layout.force(...).drag()
      
      On browsers like Internet Explorer 11, the <svg:use>
      EventTarget is represented by a SVGElementInstance that looks
      like this:
      
          [object SVGElementInstance]
             {
                [functions]: ,
                __proto__: { },
                childNodes: { },
                constructor: { },
                correspondingElement: { },
                correspondingUseElement: { },
                firstChild: null,
                lastChild: null,
                nextSibling: null,
                parentNode: { },
                previousSibling: { }
             }
      
      No other properties such as .style are present. We must use the
      correspondingElement property to access the actual SVG element
      instantiated by the <svg:use> in order to have a successful drag.
      17cc510c
  13. 02 Jan, 2016 1 commit
  14. 17 Dec, 2015 1 commit
  15. 14 Dec, 2015 3 commits
  16. 11 Dec, 2015 1 commit
  17. 30 Nov, 2015 1 commit
  18. 25 Nov, 2015 1 commit
  19. 16 Nov, 2015 1 commit
  20. 13 Nov, 2015 1 commit
    • Mike Bostock's avatar
      Schedule first tick invocation before dispatching start event. · 629d298a
      Mike Bostock authored
      This fixes a priority inversion where a transition B that is scheduled on
      transition A’s start initializes its tweens before transition A has its first
      tick. By scheduling transition A’s first tick before dispatching A’s start
      event, it’s first tick is guaranteed to run before any new transition’s tweens
      are initialized.
      
      Related #1576 d3/d3-transition#16.
      629d298a
  21. 12 Nov, 2015 1 commit
  22. 11 Nov, 2015 1 commit
  23. 10 Nov, 2015 3 commits