dist/doc/changelog.html

<!DOCTYPE html>
<html>
    <head>
        <meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<meta http-equiv="content-type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1, maximum-scale=1, user-scalable=no"/>
        <link rel="shortcut icon" type="image/png" href="../img/favicon.png">
        <title></title>

        
<link href="//maxcdn.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap.min.css" rel="stylesheet">
<link href="//netdna.bootstrapcdn.com/font-awesome/4.0.3/css/font-awesome.css" rel="stylesheet">
<link href="//fonts.googleapis.com/css?family=Lato:400,700" rel="stylesheet">
<link rel="stylesheet" href="../css/main.css">
        <link rel="stylesheet" href="../css/jsplumb-doc.css">

    </head>
    <body>
        <div class="navbar navbar-top navbar-fixed-top" role="navigation">
    <div class="container">
        <div class="navbar-header">
            <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
                <span class="sr-only">Toggle navigation</span>
                <span class="icon-bar"></span>
                <span class="icon-bar"></span>
                <span class="icon-bar"></span>
            </button>

            <a class="navbar-brand" href="/"><img src="../../img/logo-medium-jsplumb.png"></a>
            <div class="community"></div>

        </div>

        <div class="navbar-collapse collapse nav-wrapper">
            <ul class="nav navbar-nav">
                <li><a href="../">DEMOS</a></li>
                <li><a href="../doc/home.html">DOCS</a></li>
                <li><a href="../apidocs/index.html">API</a></li>
                <li><a href="../download">DOWNLOAD</a></li>
                <li><a href="http://beta.jsplumbtoolkit.com/contact.html">CONTACT</a></li>
                <li><a href="https://blog.jsplumbtoolkit.com">BLOG</a></li>

            </ul>

            <div class="social-nav hidden-xs">
                <a href="http://twitter.com/jsplumblib" class="link"><span class="icon-twitter"></span></a>
                <a href="http://github.com/sporritt/jsplumb/" class="link"><span class="icon-github"></span></a>
                <a href="http://www.linkedin.com/company/jsplumb" class="link"><span class="icon-linkedin"></span></a>

            </div>
        </div><!--/.nav-collapse -->
    </div>
</div>

        <div class="container padding-top">
            <div class="row" id="docs">
                <div class="docs-nav col-xs-3" tabindex="0">
                    <ul>
<li><a href="changelog.html">Changelog</a></li>
<li>Required imports and basic setup<ul>
<li><a href="home.html#browser">Browser Compatibility</a></li>
<li><a href="home.html#setup">Setup</a></li>
<li><a href="home.html#doctype">Doctype</a></li>
<li><a href="home.html#imports">Required Imports</a></li>
<li><a href="home.html#initializing">Initializing jsPlumb</a></li>
<li><a href="home.html#multiple">Multiple jsPlumb Instances</a></li>
<li><a href="home.html#zindex">Z-Index Considerations</a></li>
<li><a href="home.html#container">Where does jsPlumb add elements?</a></li>
<li><a href="home.html#dragging">Element Dragging</a></li>
<li><a href="home.html#performance">Performance</a></li>
<li><a href="zooming.html">Zooming</a></li>
</ul>
</li>
<li><a href="defaults.html">Configuring Defaults</a></li>
<li><a href="basic-concepts.html">Basic Concepts</a><ul>
<li><a href="anchors.html">Anchors</a></li>
<li><a href="connectors.html">Connectors</a></li>
<li><a href="endpoints.html">Endpoints</a></li>
<li><a href="overlays.html">Overlays</a></li>
</ul>
</li>
<li><a href="connections.html">Establishing Connections</a><ul>
<li><a href="connections.html#programmatic">Programmatic Connections</a></li>
<li><a href="connections.html#common">Reusing Common Settings</a></li>
<li><a href="connections.html#detaching">Detaching Programmatic Connections</a></li>
<li><a href="connections.html#draganddrop">Drag and Drop Connections</a></li>
<li><a href="connections.html#sourcesandtargets">Elements as sources &amp; targets</a></li>
<li><a href="connections.html#maketarget">Element Targets</a></li>
<li><a href="connections.html#makesource">Element Sources</a></li>
<li><a href="connections.html#sourcefilter">Specifying drag source area</a></li>
</ul>
</li>
<li><a href="removing.html">Removing Connections/Endpoints</a></li>
<li><a href="parameters.html">Connection &amp; Endpoint Parameters</a></li>
<li><a href="types.html">Connection &amp; Endpoint Types</a></li>
<li><a href="events.html">Events</a><ul>
<li><a href="interceptors.html">Interceptors</a></li>
</ul>
</li>
<li>Appearance<ul>
<li><a href="paint-styles.html">Styling via Paint Styles</a></li>
<li><a href="styling-via-css.html">Styling via CSS</a></li>
</ul>
</li>
<li><a href="querying.html">Querying jsPlumb</a></li>
<li><a href="animation.html">Animation</a></li>
<li><a href="utilities.html">Utility Functions</a></li>
<li><a href="loader-support.html">Loader Support (RequireJS)</a></li>
<li>Examples<ul>
<li><a href="connect-examples.html">jsPlumb.connect</a></li>
<li><a href="draggable-connections-examples.html">Draggable Connections</a></li>
<li><a href="miscellaneous-examples.html">Miscellaneous</a></li>
</ul>
</li>
<li>Development<ul>
<li><a href="development.html">Which files are which?</a></li>
<li><a href="Build.html">Building jsPlumb</a></li>
<li><a href="development-documentation.html">Documentation while developing</a></li>
</ul>
</li>
</ul>
                </div>
                <div class="markdown-body col-xs-9">
                    <h2>2.2.7</h2>

<p>10 December 2016</p>

<ul>
<li>fixed an issue with setting a blank label on a Label overlay.</li>
</ul>

<h2>2.2.6</h2>

<p>05 November 2016</p>

<ul>
<li>fix deployment issue in 2.2.6</li>
</ul>

<h2>2.2.5</h2>

<ul>
<li>upgrade to mottle 0.7.4 </li>
</ul>

<h2>2.2.4</h2>

<ul>
<li>no code change from 2.2.3. built to provide initial build in the bower-jsplumb repo.</li>
</ul>

<h2>2.2.3</h2>

<ul>
<li>add support for connectionType to makeTarget call (to allow multiple types of target)</li>
</ul>

<h2>2.2.2</h2>

<ul>
<li>corrected deployment issue in 2.2.1. 2.2.1 does not do what it says; it is an impostor.</li>
</ul>

<h2>2.2.1</h2>

<ul>
<li><p>upgrade to Katavorio 0.18.0; now <code>rank</code> is supported in <code>dropOptions</code> to <code>makeTarget</code> or <code>addEndpoint</code>. Use this when
you want to make a Group container a connection target but you want to give prededence to Nodes inside the Groups.</p></li>
<li><p>set drop rank for Group elements automatically (if user does not provide one) so that Nodes receive drop events before
Groups.</p></li>
</ul>

<h2>2.2.0</h2>

<ul>
<li>Overhaul of keys used in paintStyle and hoverPaintStyle objects:</li>
</ul>

<p>strokeStyle   -&gt; stroke
  fillStyle     -&gt; fill
  lineWidth     -&gt; strokeWidth
  outlineColor  -&gt; outlineStroke
  outlineWidth  -&gt; outlineWidth     (yes, unchanged)</p>

<ul>
<li><p>All classnames changed from <code>jsplumb-</code> prefix to <code>jtk-</code>, to bring them into line with the prefix used by the Toolkit edition.</p></li>
<li><p>support webpack</p></li>
<li><p>add webpack demo page</p></li>
<li><p>upgrade to Mottle 0.7.3</p></li>
<li><p>upgrade to Katavorio 0.17.0</p></li>
<li><p>straight connectors extracted to a separate JS file for dev</p></li>
<li><p>added disable/enable functionality example to sources and targets demo</p></li>
</ul>

<h2>2.1.6</h2>

<ul>
<li>setTargetEnabled/setSourceEnabled now return the previous value of the enabled state.</li>
<li>disabled source/target elements get a <code>jtk-source-disabled</code> or <code>jtk-target-disabled</code> class added.</li>
<li>issue 552 - in place endpoint painted in wrong location during connection drag</li>
<li>issue 554 - after drag, connections to a node inside a group are positioned incorrectly.</li>
</ul>

<h2>2.1.5</h2>

<ul>
<li>issue 533 - Dragging multiple nodes causes incorrect connectors position</li>
<li><code>reset</code> method sets hover suspended flag to false now.</li>
</ul>

<h2>2.1.4</h2>

<ul>
<li>issue 530 - Further fix related to issue 530, in which elements that had connections prior to being added to a group
were sometimes getting an offset applied when dragging. The fix for this removed some code that was put in for issue 231, 
but it turns out the fix for issue 231 had broken somewhere along the line and this change set that right too.</li>
</ul>

<h2>2.1.3</h2>

<ul>
<li>issue 530 - Element with existing connections being added to Groups.</li>
<li>issue 526 - bower version incorrect</li>
</ul>

<h2>2.1.2</h2>

<ul>
<li>issue 523 - Endpoint click registration problems</li>
<li>issue 522 - Groups documentation</li>
</ul>

<h2>2.1.1</h2>

<ul>
<li>bugfix for groups: element exposed now via getEl method, not directly as el. </li>
</ul>

<h2>2.1.0</h2>

<ul>
<li>&#39;elementDraggable&#39; event now fired whenever an element is made draggable via the <code>draggable</code> function</li>
<li>add support for &#39;groups&#39; - elements that can contain other elements, and which are collapsible.</li>
<li><p>upgrade to Mottle 0.7.2. a few fixes for event delegation.</p></li>
<li><p>upgrade to katavorio 0.17.0</p></li>
<li><p>upgrade to mottle 0.7.2</p></li>
<li><p>upgrade to jsBezier 0.8</p></li>
<li><p>upgrade to Biltong 0.3</p></li>
</ul>

<p>ISSUES</p>

<ul>
<li>483 - srcElement undefined in Firefox</li>
<li>484 - changed a couple of variables refs so that they are not reserved words </li>
</ul>

<h2>2.0.6</h2>

<ul>
<li><p>add <code>connectionAborted</code> event, fired whenever a new connection is abandoned before being dropped on an endpoint or
target. also fired if <code>beforeDrop</code> interceptor returns false.</p></li>
<li><p>fixed docs for <code>connectionDetached</code> to call out the fact that it is not fired when a connection is abandoned.</p></li>
</ul>

<p>ISSUES</p>

<ul>
<li>472 - Pending connections do not fire the documented events</li>
<li>469 - Scopes not applied to new drag &amp; drop connections</li>
<li>452 - Why &quot;connection.scope&quot; property cannot get scope value ?</li>
</ul>

<h2>2.0.5</h2>

<ul>
<li><p>Refactor Bezier and StateMachine connectors to extend common AbstractBezierConnector parent. This means Bezier
connectors now support loopback connections.</p></li>
<li><p>add support for loopback connections to Flowchart connector (issue 457).</p></li>
</ul>

<p>ISSUES</p>

<ul>
<li><p>458 connectionDetached is fired the first time only</p></li>
<li><p>457 &#39;Flowchart&#39; connector: loopback connections broken</p></li>
<li><p>451 cannot bind events to arrow overlays</p></li>
<li><p>446 addClass and removeClass on Endpoint and Connection now also add/remove class from their overlays, by default. This
can be overridden by providing &#39;true&#39; as the second argument to the addClass/removeClass methods.</p></li>
<li><p>434 wrong arrow drawing (offset) when creating a connection on IE9 </p></li>
</ul>

<h2>2.0.4</h2>

<ul>
<li>upgrade to Katavorio 0.13.0</li>
<li>upgrade to Mottle 0.7.1</li>
<li>add <code>droppable</code> method to jsPlumbInstance: the ability to make <em>elements</em> droppable. Not connections or endpoints - DOM 
elements.</li>
<li>fixes for offset calculation when dragging a nested element.</li>
</ul>

<h2>2.0.3</h2>

<h3>Issues</h3>

<ul>
<li>444 - maxConnections not honoured in makeSource</li>
</ul>

<h3>Backwards Compatibility</h3>

<ul>
<li><code>removeFromPosse</code> now requires the ID of the Posse, since the new Katavorio version supports multiple Posses
per element.</li>
</ul>

<h3>New Functionality</h3>

<ul>
<li>Upgrade to Katavorio 0.12.0, with support for multiple Posses and active/passive elements in a Posse.</li>
<li><code>removeFromAllPosses(element)</code> method added.</li>
</ul>

<h3>Miscellaneous</h3>

<ul>
<li><p>Fixed an issue in which overlays on Endpoint types were not being converted to &#39;full&#39; syntax upon registration. This was
an internal issue that could manifest in user code occasionally.</p></li>
<li><p>We now ensure drag scope is set on an element when source scope changes, even though the code can derive source scope
when the user begins to drag. The Toolkit edition makes use of this new update.</p></li>
</ul>

<h2>2.0.2</h2>

<p>Fix issues with CSS class documentation.</p>

<h2>2.0.1</h2>

<p>Bugfix release: connectionDetached event was no longer firing.</p>

<h2>2.0.0</h2>

<h3>Backwards Compatibility</h3>

<ul>
<li>Removal of the VML renderer. IE8 no longer supported.</li>
<li>All class names such as <code>_jsPlumb_connector</code> renamed to, for example, <code>jsplumb-connector</code>.</li>
<li>makeSource and makeTarget require explicit anchor/endpoint parameters: they do not source these things
from the jsPlumb Defaults.</li>
</ul>

<h3>New Functionality</h3>

<ul>
<li>makeSource now supports multiple registrations per element, keyed by the <code>connectionType</code> parameter.  You can configure 
elements to be connection sources for different connection types, and also when you call <code>connect</code> with a <code>type</code> 
parameter that matches a <code>makeSource</code> registration, that type will be used.</li>
<li>new connection drag: if the type of connection is known, that type&#39;s target endpoint is now used.</li>
<li>addition of support for <code>dragProxy</code> to endpoint/makeSource: an endpoint spec defining what the drag endpoint should 
look like when dragging a new connection. The existence of a <code>dragProxy</code> will override any other behaviour (such as the 
behaviour discussed in the point above)</li>
<li>addition of &quot;posses&quot; - groups of elements that should always be dragged together.</li>
<li>when dragging a new connection, jsPlumb now uses as the source endpoint a true representation of what the endpoint
will be if a connection is established. Previous versions just used a static, in-place, endpoint.</li>
</ul>

<h2>1.7.10</h2>

<h3>Changes between 1.7.9 and 1.7.10</h3>

<ul>
<li>Small update to getOffset to make it return the correct value if the input element was the container itself.</li>
<li>Small update to animation to fix incorrect falsey check.</li>
<li>Documented the <code>on</code> method of a <code>jsPlumbInstance</code> in the API docs.</li>
<li><code>on</code> and <code>off</code> event registration methods now return the current jsPlumb instance</li>
</ul>

<h2>1.7.9</h2>

<h3>Changes between 1.7.8 and 1.7.9</h3>

<ul>
<li>No more jQuery flavour. Vanilla jsPlumb is the only jsPlumb, and as such, has been renamed to simply <code>jsPlumb-1.7.9.js</code>.</li>
<li>First version of jsPlumb to be published to npm.</li>
<li>Addition of getManagedElements method. Returns a map of all the elements the instance of jsPlumb is currently managing.</li>
</ul>

<h4>Issues</h4>

<ul>
<li><strong>421</strong> svg gradient elements not cleaned up properly</li>
</ul>

<h2>1.7.8</h2>

<h3>Changes between 1.7.7 and 1.7.8</h3>

<h4>Issues</h4>

<ul>
<li><strong>381</strong> -  instance.detach(connection) will detach source endpoint as well</li>
<li><strong>419</strong> -  endpoints not cleaned up properly when connection converted to looback to endpoints not cleaned up properly when connection converted to loopback</li>
<li><strong>420</strong> - Image endpoint not cleaned up correctly</li>
</ul>

<h2>1.7.7</h2>

<h3>Changes between 1.7.6 and 1.7.7</h3>

<h4>Issues</h4>

<ul>
<li><strong>408</strong> - setIdChanged doesn&#39;t correctly handle element sources/targets</li>
<li><strong>410</strong> - setConnector (whether applied via type or directly) removes custom css classes of other types</li>
<li><strong>412</strong> - Endpoint style cannot be transparent </li>
<li><strong>415</strong> - Unnecessary endpoint may be created at when drag and drop endpoint from one node to another.</li>
</ul>

<h2>1.7.6</h2>

<h3>Changes between 1.7.5 and 1.7.6</h3>

<p>A minor bugfix release, with a few new options for controlling connection detachment (and one small backwards 
compatibility issue to be aware of)</p>

<h4>Backwards Compatibility</h4>

<ul>
<li>All versions of jsPlumb prior to 1.7.6 would fire <code>beforeDetach</code> for both new Connection drags and also 
dragging of existing Connections. As of 1.7.6 this latter behaviour has been moved to the <code>beforeStartDetach</code> 
interceptor.</li>
</ul>

<h4>New Functionality</h4>

<ul>
<li><p><code>revalidate</code> now supports the same arguments as repaint - an ID, an Element, or a list-like
object (such as the results of $(..) or document.querySelectorAll)</p></li>
<li><p>added <code>beforeStartDetach</code> interceptor: a function that is called before an existing connection is dragged off of 
one of its endpoints, and which can return false to cancel the drag.</p></li>
<li><p>The <code>unbind</code> method on various objects (jsPlumbInstance, Connection, Endpoint to name a few) now supports passing a 
Function to be unbound, rather than just some event name.</p></li>
<li><p>Connectors now have a <code>getLength</code> function, which returns their length in pixels. To access from a Connection,
  you need to first get the connector: <code>someConnection.getConnector().getLength()</code></p></li>
</ul>

<h4>Issues</h4>

<ul>
<li><strong>350</strong> - recalculateOffsets not working</li>
<li><strong>353</strong> - multiple select disabled</li>
<li><strong>367</strong> - rendering and drag/drop errors when parent element scrolled</li>
<li><strong>369</strong> - unbinding events</li>
<li><strong>383</strong> - jsPlumb.setDraggable fails for getElementsByClassName return value</li>
<li><strong>392</strong> - onMaxConnections jpc isn&#39;t defined</li>
<li><strong>402</strong> - offset update cache</li>
<li><strong>404</strong> - statemachine demo makes ghost endpoints</li>
</ul>

<h2>1.7.5</h2>

<h3>Changes between 1.7.4 and 1.7.5</h3>

<p>A minor-ish release; no changes to the API. Some refactoring of JS and of CSS. But one notable thing is that touch events on Windows touch laptops are working now (in Chrome and IE; FF seems to still have issues)</p>

<h4>Backwards Compatibility</h4>

<ul>
<li>The jQuery flavour was removed from the <code>main</code> section in <code>bower.json</code>.</li>
</ul>

<h4>Issues</h4>

<ul>
<li><strong>295</strong> - draggable not working in chrome</li>
<li><strong>340</strong> - Draggable stop event doesn&#39;t get called on all elements when dragging multiple elements</li>
<li><strong>341</strong> - Add possibility to change z-order of the &quot;inPlaceCopy&quot; endpoint.</li>
<li><strong>344</strong> - add getUuids method to Connection</li>
<li><strong>345</strong> - Error when two linked objects are with exactly same position</li>
</ul>

<h2>1.7.4</h2>

<h3>Changes between 1.7.3 and 1.7.4</h3>

<h4>Issues</h4>

<ul>
<li><strong>237</strong> - scroll is ignored in offset calculations</li>
<li><strong>314</strong> - jsPlumbUtil is not defined (webpack)</li>
<li><strong>329</strong> - Scroll issue</li>
<li><strong>332</strong> - endpoint label not working in newest version</li>
<li><strong>333</strong> - ReattachConnections not working when a connection is detached (jquery &amp; vanilla 1.7.3)</li>
<li><strong>336</strong> - cannot drop a connection back on the endpoint to which it was previously attached</li>
</ul>

<h2>1.7.3</h2>

<h3>Changes between 1.7.2 and 1.7.3</h3>

<p>Predominantly a minor bugfix release, this version brings a degree of uniformity to the behaviour of elements configured with <code>makeSource</code> and <code>makeTarget</code>, and is a recommended upgrade if you are currently using any other 1.7.x version.</p>

<h4>New Functionality</h4>

<ul>
<li>There is a new interceptor in this release: <code>beforeDrag</code>.  You can use it to abort dragging a connection as soon as it starts, and also to supply the initial data for a Connection that uses a parameterized type.</li>
<li>Added <code>jsPlumb.empty</code> function: remove child content from a node, including endpoints and connections, but not the element itself.</li>
</ul>

<h4>Backwards Compatibility</h4>

<ul>
<li>The <code>doWhileSuspended</code> method has been aliased as <code>batch</code>, and <code>doWhileSuspended</code> is now deprecated, to be removed in version 2.0.0.</li>
</ul>

<h4>Issues</h4>

<ul>
<li><strong>187</strong> - jsPlumb.draggable() doesn&#39;t work with forms</li>
<li><strong>281</strong> - beforeDetach not triggered by <code>jsPlumb.detachAllConnections</code></li>
<li><strong>287</strong> - Cannot drop source of connection on makeTarget element after 1.6.4</li>
<li><strong>289</strong> - Cannot prevent drop of source edge using beforeDrop on nested makeTarget elements</li>
<li><strong>297</strong> - Distinguish drag\click for Vanilla jsPlumb</li>
<li><strong>298</strong> - Fix for using library inside shadowDom (e.g. Polymer etc.)</li>
<li><strong>307</strong> - Setting Container multiple times fires events multiple times</li>
<li><strong>311</strong> - addType resets overlays</li>
<li><strong>313</strong> - setContainer does not work when container has overflow: scroll;</li>
<li><strong>315</strong> - setConnector removes existing overlays</li>
<li><strong>317</strong> - Docs incorrectly refer to &quot;mouseenter&quot;</li>
<li><strong>326</strong> - Connections not updating position - (detach, delete, readd, reconnect)</li>
</ul>

<h2>1.7.2</h2>

<h3>Changes between 1.7.1 and 1.7.2</h3>

<ul>
<li>Reverted a minor bugfix introduced by the fix for issue 276</li>
<li>Updated continuous anchors to allow for several Continuous anchors to be in use on the one element.</li>
</ul>

<h2>1.7.1</h2>

<h3>Changes between 1.7.0 and 1.7.1</h3>

<h4>Issues</h4>

<ul>
<li><strong>276</strong> - TypeError on dragging empty target endpoint</li>
</ul>

<h2>1.7.0</h2>

<h3>Changes between 1.6.4 and 1.7.0</h3>

<h4>Backwards Compatibility</h4>

<ul>
<li><p>Perhaps the biggest change between 1.6.4 and 1.7.0 is that YUI and MooTools are no longer supported.  It is recommended you use vanilla jsPlumb now. jQuery is still supported but it is neither as fast nor does it have as many features as vanilla jsPlumb.</p></li>
<li><p>The <code>parent</code> argument to the <code>makeSource</code> function is no longer supported. It was being kept because neither YUI nor MooTools have the ability to support a drag filter, but now that those libraries are not supported this feature has been removed.  The <code>filter</code> approach is much more powerful.</p></li>
</ul>

<h4>New Functionality</h4>

<p>Perhaps not strictly new functionality, but shiny enough to warrant being associated with the word &quot;new&quot;, is the fact that jsPlumb 1.7.0 is considerably faster than any previous version.  A rough comparison: the default settings for the load test in jsPlumb generate 360 connections in total between 10 elements. in 1.6.4 this test averages about 1600ms in Chrome on a Mac.  In 1.7.0 that number is about 600ms on the same computer.</p>

<h4>Issues</h4>

<ul>
<li><strong>178</strong> - Detachable endpoints: different behaviour between connect() and mouse-based connections</li>
<li><strong>214</strong> - Endpoint stays visible when should be terminated (right mouse button)</li>
<li><strong>242</strong> - Distinguish drag\click for Vanilla jsPlumb</li>
<li><strong>245</strong> - reinstate isConnectedTo method on Endpoint</li>
<li><strong>246</strong> - outlineColor ignored when gradient defined in paintStyle<br></li>
<li><strong>248</strong> - dynamic anchor create fail</li>
<li><strong>257</strong> - allow for the scope of a makeSource element to be changed</li>
<li><strong>258</strong> - Typo in documentation: s/container/Container </li>
<li><strong>260</strong> - isSource and isTarget usage with makeSource and makeTarget causes broken connections</li>
<li><strong>261</strong> - Two target endpoints close to each other: &quot;TypeError: Cannot read property &#39;0&#39; of null&quot;</li>
<li><strong>262</strong> - hoverPaintStyle only works for the first connection (maxConnections &gt; 1) </li>
<li><strong>263</strong> - TypeError: conn.endpoints is null</li>
<li><strong>267</strong> - continuous anchors with faces set do not paint on selected faces when not connected to anything</li>
<li><strong>268</strong> - Endpoint &quot;Blank&quot; generates endpoint with class &quot;undefined&quot;</li>
<li><strong>269</strong> - Source endpoint does not/cannot respect uniqueEndpoint setting</li>
<li><strong>270</strong> - Support <code>endpointStyle</code> in args to addEndpoint and makeSource/makeTarget</li>
</ul>

<h2>1.6.4</h2>

<h3>Changes between 1.6.3 and 1.6.4</h3>

<h4>Backwards Compatibility</h4>

<ul>
<li>No issues</li>
</ul>

<h4>New Functionality</h4>

<ul>
<li>Connection types support &#39;anchor&#39; and &#39;anchors&#39; parameters now.</li>
</ul>

<h4>Miscellaneous</h4>

<ul>
<li>YUI adapter now sets a &#39;base&#39; url and retrieves everything via https.</li>
</ul>

<h2>1.6.3</h2>

<h3>Changes between 1.6.2 and 1.6.3</h3>

<h4>Backwards Compatibility</h4>

<ul>
<li>No issues</li>
</ul>

<h4>New Functionality</h4>

<ul>
<li>Added optional <code>allowLoopback</code> boolean parameter to vanilla jsPlumb&#39;s <code>makeTarget</code> method. </li>
<li>When using parameterized types, unmatched values are now replaced with blank strings, rather than being left in place. For instance, if you had <code>label=&quot;${foo}&quot;</code>, and you passed a blank &#39;foo&#39; value, you used to see <code>&quot;${foo}&quot;</code>. Now you see <code>&quot;&quot;</code>.</li>
<li>You can set <code>visible:false</code> on an overlay spec, to have it initially invisible.</li>
<li>Added <code>setHoverEnabled</code> method to jsPlumb.</li>
<li>Added <code>clearTypes</code> method to Connection and Endpoint</li>
<li>Connection and Endpoint types now support <code>cssClass</code> property. These are merged into an array if multiple types declare a cssClass.</li>
</ul>

<h3>Issues</h3>

<ul>
<li><strong>222</strong> - Endpoints incorrectly calculated when the anchor faces of source/target are set to left/right</li>
<li><strong>223</strong> - beforeDetach not fired by jsPlumb</li>
<li><strong>224</strong> - endpointStyle of the jsPlumb.connect method does not work</li>
<li><strong>227</strong> - MaxConnections=1 console log error</li>
<li><strong>230</strong> - Endpoints not cleaned up after connector move</li>
<li><strong>236</strong> - makeTarget/makeSource drag issues</li>
<li><strong>241</strong> - Dropping existing connection creates an orphaned endpoint when beforeDrop returns false</li>
<li><strong>243</strong> - setConnector not correctly re-assigning event handler on overlays</li>
</ul>

<h2>1.6.2</h2>

<h3>Changes between 1.6.1 and 1.6.2</h3>

<h4>Backwards Compatibility</h4>

<ul>
<li><p>1.6.2 has improved behaviour for determining what element to use as the Container. Previous 1.6.x versions defaulted to the document body, with the docs strongly recommending you set a Container. From 1.6.2, if there is no Container set when the user makes a first call to either addEndpoint, makeSource, makeTarget or connect, the Container is set to be the offsetParent of either the element being configure (in the case of <code>addEndpoint</code>, <code>makeSource</code> and <code>makeTarget</code>), or the source element, for the <code>connect</code> method.</p></li>
<li><p>a consequence of this is that you can no longer manipulate <code>Defaults.Container</code> manually. Your changes will be ignored; <code>Defaults.Container</code> is referenced only in the constructor or in the <code>importDefaults</code> method. If you need access to the current Container, use the <code>getContainer</code> method.</p></li>
<li><p>the order of parameters to the function <code>jsPlumbInstance.on</code> has changed, in the case that you are passing 4 parameters and using it for event delegation.  Previously, the order was <code>(element, filter, eventId, callback)</code> and now the order is <code>(element, eventId, filter, callback)</code>. This brings it into line with the order of parameters in jQuery&#39;s <code>on</code> function.  It is not very likely this will affect you: <code>jsPlumbInstance.on</code> is used internally, mostly (although it can be used to register events independently of jsPlumb if you want to use it).</p></li>
</ul>

<h3>New Functionality</h3>

<ul>
<li>The Container inferencing discussed above is both a backwards compatibility issue and also new functionality!</li>
<li>added <code>setContainer</code>, to allow you to move an entire jsPlumb UI to some new parent</li>
<li>added <code>getContainer</code>, to allow you to retrieve the current Container.</li>
</ul>

<h3>Issues</h3>

<ul>
<li><strong>207</strong> - problem with absolute overlays</li>
<li><strong>211</strong> - setVisible(true) on hidden overlay whose connection has moved causes the overlay to repaint in the wrong place</li>
</ul>

<h2>1.6.1</h2>

<p>This is a minor release in which a few issues related to zooming have been fixed.</p>

<h3>Changes between 1.6.0 and 1.6.1</h3>

<h4>Backwards Compatibility</h4>

<p>No issues</p>

<h4>Issues</h4>

<ul>
<li><strong>206</strong> Fix documentation error about jsPlumb.Defaults.Endpoints</li>
</ul>

<h4>New Functionality</h4>

<p>Better handling of zooming in vanilla jsPlumb.</p>

<h2>1.6.0</h2>

<p>Version 1.6.0 is a major release of jsPlumb. With this version ships a &quot;vanilla&quot; version - it relies on no external libraries, and also has a few features that the other library adapters do not (see below). </p>

<h3>Changes between 1.5.5 and 1.6.0</h3>

<h4>Backwards Compatibility</h4>

<ul>
<li>There is no support for the canvas renderer in jsPlumb 1.6.0.</li>
<li>The way in which library adapters inject their functionality into jsPlumb has changed. This will affect very few people; contact jsPlumb if you need help with this.</li>
<li>All elements added by jsPlumb are appended to the current &quot;Container&quot;, which defaults to the document body. This differs from previous versions, in which if there was no Container set then jsPlumb would append elements to the parent of a connection&#39;s source endpoint. For this reason it is now more than ever recommended that you set a Container.<br></li>
<li>The <code>container</code> parameter on <code>addEndpoint</code> or <code>connect</code> calls is no longer supported.</li>
</ul>

<h4>Issues</h4>

<ul>
<li><strong>91</strong>  - Old ID is being used on events after setId</li>
<li><strong>143</strong> - SVG gradient fails when page url already contains a hash</li>
<li><strong>153</strong> - jsPlumb.animate no longer supports jQuery selectors</li>
<li><strong>157</strong> - connectionMoved event not fired (when using makeTarget)</li>
<li><strong>162</strong> - Connector &#39;Flowchart&#39; occurs an error.</li>
<li><strong>164</strong> - makeSource fails when used in conjunction with uniqueEndpoint</li>
<li><strong>173</strong> - jsPlumb.setDraggable([element_id],false); fails</li>
<li><strong>177</strong> - Flowchart straight Line</li>
<li><strong>202</strong> - Spurious mouse events in connector with outline</li>
<li><strong>203</strong> - hoverClass on endpoints doesn&#39;t work</li>
</ul>

<h4>New Functionality</h4>

<h5>DOM Adapter</h5>

<p>It isn&#39;t actually true to say that this adapter has no external dependencies; it actually relies on a couple of new projects written specifically for this (<a href="https://github.com/jsplumb/mottle">Mottle</a> for events, and <a href="https://github.com/jsplumb/katavorio">Katavorio</a> for drag/drop support. However, these dependencies are wrapped into the concatenated jsPlumb 1.6.0 JS file.</p>

<h6>Multiple element dragging</h6>

<p>The DOM adapter supports dragging (and dropping!) multiple elements at once.</p>

<h6>Multiple drag/drop scopes</h6>

<p>Also supported are multiple scopes for each draggable/droppable element.</p>

<h6>Using Vanilla jsPlumb with jQuery</h6>

<p>Even if you have jQuery in the page you can use vanilla jsPlumb; it will accept jQuery selectors as arguments. Keep in mind that you won&#39;t get jQuery selectors out of it, though - any methods that return an Element will return plain DOM Elements and you&#39;ll need to turn them in jQuery selectors yourself.</p>

<h4>Miscellaneous</h4>

<ul>
<li>Events now have <code>this</code> set correctly</li>
<li>Added qUnit tests for Vanilla, YUI and MooTools adapters</li>
<li>Various YUI and MooTools methods were upgraded to support passing in an element list (<code>setId</code> for one)</li>
<li>Added setSource/setTarget methods, allowing you to retarget a Connection programmatically.</li>
<li>Reduced the amount of functionality that is delegated to a support library</li>
<li>Rewrote the way support libraries are integrated</li>
</ul>

<h2>1.5.5</h2>

<h3>Changes between 1.5.4 and 1.5.5</h3>

<h4>Issues</h4>

<ul>
<li><strong>138</strong> - allow for connection type to be derived from connection params AND endpoint params.</li>
</ul>

<h2>1.5.4</h2>

<h3>Changes between 1.5.3 and 1.5.4</h3>

<h4>Issues</h4>

<ul>
<li><strong>105</strong> - Blank endpoint cleanup fails</li>
<li><strong>116</strong> - Assign anchors wont connect</li>
<li><strong>117</strong> - Assign anchors fail on source</li>
<li><strong>127</strong> - Docs on making elements draggable should note required CSS</li>
<li><strong>128</strong> - expose original event on <code>connectionDragStop</code> callback</li>
<li><strong>129</strong> - connection event fired twice by makeTarget with parent option.</li>
</ul>

<h4>New Functionality</h4>

<ul>
<li><code>&quot;Assign&quot;</code> anchors now work with the <code>makeSource</code> method.</li>
<li>The <code>connectionDragStop</code> event now supplies the original event as the second argument to the callback function.</li>
</ul>

<h4>Miscellaneous</h4>

<ul>
<li>fixed an issue causing SVG gradients to fail when a BASE tag is present in the document.</li>
</ul>

<h2>1.5.3</h2>

<h3>Changes between 1.5.2 and 1.5.3</h3>

<h4>Backwards Compatibility</h4>

<ul>
<li>The fix for issue 112 involved making a change to the circumstances under which a <code>connectionDetached</code> event is fired. When you drag the source or target of an existing connection to some other endpoint, <code>connectionDetached</code> is no longer fired. Instead, a <code>connectionMoved</code> event is fired, containing the connection that was moved, the index of the endpoint that changed (0 for source, 1 for target), and the original and new source and target endpoints.</li>
</ul>

<h4>Issues</h4>

<ul>
<li><strong>77</strong> - Endpoint types should support Anchor parameter<br></li>
<li><strong>88</strong> - reinstate labelStyle parameter on Label overlay.</li>
<li><strong>90</strong> - overlay setVisible not working (SVG/VML)</li>
<li><strong>95</strong> - Nested element positions not updated</li>
<li><strong>100</strong> - add setParent function</li>
<li><strong>101</strong> - JS error when detaching connection during connection callback</li>
<li><strong>103</strong> - IE8: connector hide does not hide overlays or background lines</li>
<li><strong>107</strong> - remove the necessity to set isSource/isTarget in order to make an endpoint draggable</li>
<li><strong>108</strong> - strange anchor orientation behaviour</li>
<li><strong>109</strong> - Dropping new connections on overlapping elements leads to crash after connection is deleted</li>
<li><strong>111</strong> - Absolute positioned arrow in wrong location</li>
<li><strong>112</strong> - Deleting a connection after changing its source endpoint causes failure.</li>
<li><strong>113</strong> - IE8 - state machine - loops are not displayed</li>
</ul>

<h4>New Functionality</h4>

<ul>
<li>A setParent function was added. jsPlumb changes the parent of some element and updates its internal references accordingly (issue 100).</li>
<li>Endpoint types now support the anchor parameter (issue 77)</li>
<li>The <code>labelStyle</code> parameter on Label overlays has made a comeback (issue 88). The argument went along the lines of it being useful if you wanted to programmatically generate a label style.</li>
<li>jsPlumb now automatically updates the internal offsets of some element that has draggable children (obviating the need for you to call <code>recalculateOffsets</code> yourself).</li>
<li>When making a programmatic connection to an endpoint that was not marked <code>isSource:true</code> or <code>isTarget:true</code>, if the connection is detachable then the endpoint is made draggable, in order to allow users to drag the connection to detach it. Connections dragged off of source or target endpoints in this way can be dropped back onto their original endpoint or onto other endpoints with the same scope, but you cannot subsequently drag a new connection from an endpoint that has been made draggable by this method.</li>
<li><code>connectionMoved</code> event added. This is fired whenever the source or target of an existing connection is dragged to some other Endpoint.</li>
</ul>

<h4>Miscellaneous</h4>

<ul>
<li><p>An issue was fixed that was preventing the ability to supply a dynamic anchor with parameters, eg</p>

<p><code>[ [ [ 1,0,0,1], [1,1,1,1] ], { selector:function() { ... } } ]</code></p></li>
</ul>

<h2>1.5.2</h2>

<h3>Changes between 1.5.1 and 1.5.2</h3>

<h4>Backwards Compatibility</h4>

<ul>
<li>Issue 86, fixed in 1.5.2, changes the priority in which parameters are applied to a connection. The documentation has always stated that source takes priority, but in fact the code was the other way round, with target taking priority. Now source does take priority.</li>
</ul>

<h4>Issues</h4>

<ul>
<li><strong>84</strong> - jsPlumb 1.5.1 Arrow Disappears on IE8 when connector is straight</li>
<li><strong>85</strong> - dragging target endpoints created by makeTarget not working</li>
<li><strong>86</strong> - Connection parameters override order</li>
</ul>

<h4>Miscellaneous</h4>

<ul>
<li>An issue that caused the SVG renderer to paint overlays before the connector was ready when the types API was used was also fixed.</li>
</ul>

<h2>1.5.1</h2>

<h3>Changes between 1.5.0 and 1.5.1</h3>

<h4>Issues</h4>

<ul>
<li><strong>81</strong> - Uncaught TypeError: Cannot read property &#39;uuid&#39; of null</li>
<li><strong>82</strong> - Blank endpoint doesn&#39;t cleanup properly</li>
<li><strong>83</strong> - for connections made with makeTarget originalEvent is not set</li>
</ul>

<h2>1.5.0</h2>

<h3>Changes between 1.4.1 and 1.5.0</h3>

<p>Release 1.5.0 contains several bugfixes and one or two minor enhancements, but the biggest change since 1.4.1 is the way jsPlumb handles inheritance internally - it has switched from a &#39;module pattern&#39; architecture to a prototypal-based setup.  The module pattern is good for information hiding, but it makes objects bigger, and its far easier to leak memory with that sort of arrangement than it is with a prototypal inheritance scheme. </p>

<p>The build has been switched from the original Ant build to Grunt with release 1.5.0, and with this has come the ability to 
build versions of jsPlumb that omit functionality you do not need (see <a href="Build">here</a>).</p>

<ol>
<li><a href="#backwards">Backwards Compatibility</a></li>
<li><a href="#new">New Functionality</a></li>
<li><a href="#issues">Issues Fixed</a></li>
<li><a href="#misc">Miscellaneous</a></li>
</ol>

<p><a name="backwards"></a></p>

<h3>Backwards Compatibility</h3>

<ul>
<li><code>jsPlumb.addClass</code>, <code>jsPlumb.removeClass</code> and removed <code>jsPlumb.hasClass</code> removed. You don&#39;t need these. You can use the methods from the underlying library.</li>
<li><code>makeTargets</code> method removed from jsPlumb. You can pass an array or selector to <code>makeTarget</code>.</li>
<li><code>makeSources</code> method removed from jsPlumb. You can pass an array or selector to <code>makeSource</code>.</li>
<li><code>jsPlumb.detach</code> no longer supports passing in two elements as arguments.  Use instead either </li>
</ul>

<p><code>jsPlumb.detach({source:someDiv, target:someOtherDiv});</code></p>

<p>or</p>

<p><code>jsPlumb.select({source:someDiv, target:someOtherDiv}).detach();</code></p>

<ul>
<li><code>jsPlumbConnectionDetached</code> event, which was deprecated, has been removed. Use <code>connectionDetached</code>.</li>
<li><code>jsPlumbConnection</code> event, which was deprecated, has been removed. Use <code>connection</code>.</li>
<li><code>Endpoint.isConnectedTo</code> method removed.  it didnt work properly as it only checked for connections where the Endpoint was the source.</li>
<li>Many places in jsPlumb that used to use library-specific selectors for elements now use pure DOM elements.  It is best to re-select any elements you are getting from a jsPlumb object, even if you supplied them as a selector, as jsPlumb will have unwrapped your selector into a DOM element.</li>
</ul>

<p><a name="new"></a></p>

<h3>New Functionality</h3>

<ul>
<li><code>jsPlumb.setSuspendDrawing</code> returns the value of <code>suspendDrawing</code> <em>before</em> the call was made.</li>
<li><code>Endpoint.setElement</code> works properly now.</li>
</ul>

<p><a name="issues"></a></p>

<h3>Issues Fixed</h3>

<ul>
<li><strong>27</strong> - investigate why a new connection is created after drag<br></li>
<li><strong>37</strong> - .addClass() not working - IE8</li>
<li><strong>39</strong> - problem about connectionDrag event</li>
<li><strong>49</strong> - Calling detachEveryConnection winds up calling repaintEverything once for each endpoint</li>
<li><strong>51</strong> - arrow overlay orientation at location 1 on flowchart connectors</li>
<li><strong>54</strong> - Memory Leak Issue</li>
<li><strong>57</strong> - DOMException while dragging endpoints</li>
<li><strong>60</strong> - flowchart connector start position wrong</li>
<li><strong>63</strong>  - Flowchart midpoint=0 is ignored </li>
<li><strong>65</strong> - Uncaught exception in IE 8</li>
<li><strong>69</strong> - jsPlumb.detach(connection) is really slow with larger graphs</li>
<li><strong>72</strong> - Drag and drop connections fail to work correctly when using makeTarget</li>
<li><strong>75</strong> - changing continuous anchor is ignored</li>
<li><strong>76</strong> - jsPlumb doesn&#39;t work in XHTML documents<br></li>
</ul>

<p><a name="misc"></a></p>

<h3>Miscellaneous</h3>

<p>Nothing to report.</p>

                </div>
            </div>
        </div>

        <script>
    (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
        (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
            m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
    })(window,document,'script','//www.google-analytics.com/analytics.js','ga');

    ga('create', 'UA-49979015-1', 'auto');
    ga('send', 'pageview');

</script>


    </body>
</html>