---
layout: default
nav: dependencies
---

<div class="container">

  <a class="anchor" id="0_4_10"></a>
  <h3>Intercooler 0.4.10 - April 17th, 2015</h3>
  <ul>
    <li>
      Reworked history storage to be more stable and less leaky.
    </li>
    <li>
      Bug fixes
    </li>
  </ul>

  <a class="anchor" id="0_4_9"></a>
  <h3>Intercooler 0.4.9 - March 10th, 2015</h3>
  <ul>
    <li>
      Added the <code>ic-select-from-response</code> attribute, allowing people to select sub-elements from a
      server response to swap in.
    </li>
    <li>
      Extended the <code>ic-include</code> attribute to allow for JSON name/value pairs to be included in a
      request.
    </li>
    <li>
      Default the value of <code>ic-always-update</code> to true, so you have to opt out of content swapping now.
    </li>
    <li>
      Added the <code>ic-remove-after</code> attribute, allowing people to remove an element after a given
      interval of time cleanly.
    </li>
  </ul>

  <a class="anchor" id="0_4_8"></a>
  <h3>Intercooler 0.4.8 - January 27th, 2015</h3>
  <ul>
    <li>
      Reworked history support, with the <code>ic-push-url</code> attribute.  Renamed the <code>X-IC-SetLocation</code>
      response header to <code>X-IC-PushURL</code> to be consistent with the new attribute.
    </li>
    <li>
      Include the current URL on all intercooler requests in the <code>ic-current-url</code> parameter.
    </li>
    <li>
      For elements with no text children, apply the fadeFast transition to children only, rather than the parent.  This
      makes buttons look better if their content is wrapped in a span.
    </li>
  </ul>

  <a class="anchor" id="0_4_7"></a>
  <h3>Intercooler 0.4.7 - January 5th, 2015</h3>
  <ul>
    <li>
      Added an integrated visual debugger.
    </li>
    <li>
      Added the 'changed' modifier for ic-trigger-on events
    </li>
    <li>
      Only allow one request in flight at a time for a given element.
    </li>
    <li>
      Allow child elements to trigger parent elements separately.
    </li>
    <li>
      Added <code>ic-trigger-delay</code> attribute to delay firing a request.
    </li>
  </ul>

  <a class="anchor" id="0_4_6"></a>
  <h3>Intercooler 0.4.6 - December 30th, 2014</h3>
  <ul>
    <li>
      Added <code>ic-replace-target</code> attribute, allowing full replacement of target elements
      for situations like replacing a table row.
    </li>
    <li>
      Added the ability to target elements that are closest to a triggered element in a <code>ic-target</code> attribute
      via the <code>closest </code> prefix.
    </li>
  </ul>

  <a class="anchor" id="0_4_5"></a>
  <h3>Intercooler 0.4.5 - December 12th, 2014</h3>
  <ul>
    <li>
      Added <code>ic-on-beforeSend</code>, <code>ic-on-success</code>, <code>ic-on-error</code> and
      <code>ic-on-complete</code>
      attributes.
    </li>
    <li>
      Always swap content containing a <code>script</code> element, so things are properly reevaluated.
    </li>
  </ul>

  <a class="anchor" id="0_4_1"></a>
  <h3>Intercooler 0.4.1 - July 4th, 2014</h3>
  <ul>
    <li>Exposed <code>LeadDyno.processElements()</code> in the Javascript API</li>
    <li>Begin sending the  <code>X-HTTP-Method-Override</code> header up in intercooler requests</li>
    <li>Begin sending the  <code>X-IC-Request</code> header up in intercooler requests</li>
  </ul>

  <a class="anchor" id="0_4_0"></a>
  <h3>Intercooler 0.4.0 - June 19th, 2014</h3>
  <ul>
    <li>Added the <a href="/responses.html#http_headers"><code>X-IC-Trigger</code></a> response header to trigger client
      side event
      handlers.
    </li>
    <li>Added the <a href="/attributes/ic-confirm.html"><code>ic-confirm</code></a> attribute.</li>
    <li>Merged a fix for <a href="https://github.com/LeadDyno/intercooler-js/pull/19">an IE8 compatibility issue</a>.
    </li>
  </ul>
  <h4>Comments on 0.4.0 Release</h4>

  <p>
    The big enhancement in this release (small code change, but <strong>big</strong> functionality boost!) is the <code>X-IC-Trigger</code>
    response header, which finally solves a tricky problem I've been wrestling with: How do you communicate server side state
    changes that have client-side UI ramifications that fall outside the usual Intercooler request-and-replace
    partial view flow?
  </p>

  <p>This new mechanism allows you to cleanly separate your server side and client-side logic even in cases where the
    simple content-swapping approach isn't enough.</p>

  <p>A great example is if you want to hide a modal if and only if a form in the modal submits valid data to the
    server.  You can now easily fire an <code>server.accountCreated</code> event (as an example) from the server side
    and respond to that on the client side by hiding the modal.  Clean, crisp and very little code!</p>

  <p>You can download the latest <code>intercooler.js</code> from <a href="/download.html">the Downloads page</a>.</p>

  <p>Enjoy!</p>
</div>