0.5.0

What's Changed

• Remove coffeescript from this library by @rafaelfranca in #188

New Contributors

• @cursedcoder made their first contribution in #184
• @rafaelfranca made their first contribution in #187

Full Changelog: v0.4.8...v0.5.0

v0.4.6

This release primarily fixes bugs in some incompatibilities with redirects that occur in partial replaces introduced since 0.4.2.

v0.4.5

This release simply makes TG play nice with lazy loading in rails.

v0.4.4

This release's functionality mostly falls in two categories:

• Improving the reliability and readability of out tests
• Making redirects in a TG application more sane and more accurately detected

Changes

• #167 - More robust redirect detection (using clientside checks as well as server side)
• #173, #168, #172 - Improve test readability and reliability
• #162 - Fix scroll not being reset on redirection
• #153 - Fix moving from tracked to untracked assets
• #1160 - Fix X-XHR-Redirected-To application

v0.4.3

Changes

• #122 - Specify minimum Ruby version
• #144 - Refactor process doc; add new error
• #145 - Defend against nulls in full page navigate
• #163 - Turbolinks accepts a document and runs tests inside an iframe

v0.4.2

Changes

• #144 - Refactor process doc and simplify testing
• #145 - Defend against nulls in full page navigate
• #146 - ComponentUrl test coverage
• #152 - Ensure that all head scripts are downloaded and executed before running inline scripts on a page. Previously, users navigating quickly could cause unexpected execution of inline scripts.

v0.4.0

Head Asset Tracking Take Two

NOTE: This functionality is experimental, has changed significantly since 0.3.0, and may change again in the future before 1.0

When a <script> or <link> tag with a unique name in it's data-turbolinks-track is encountered in a response document Turbograft will insert it into the active DOM and, if it's a script, force it to execute.

If an asset with a different src/href but the same data-turbolinks-track value is found upstream, turbograft will force a full page refresh. This prevents potential multiple executions of a script bundle when a new version of your app is shipped.

As of version 0.4.0, this functionality has been made backwards compatible. If data-turbolinks-track="true" head assets are present, turbograft will cause a full page refresh when the set is changed in any way.

v0.3.1

Fixing Head Asset Tracking (and stuff)

Changes
#134 - put an end to the scourge of null url exceptions
#133 - prevent partial page replaces from trying to track head assets
#132 - work around to fix safari crazy behaviour resulting in 0 tracked assets being found and removing all of your styles (D:)

v0.3.0

Introducing Head Asset Tracking (Turbohead)

Changes
#123

• More robust js tests
• Fix flaky test breakages in ruby land
• Introducing Turbohead:
  • script and link tags in the document head with data-turbolinks-track are now managed through turbograft
  • link tags are modified using as few changes as possible to match the new set of tracked assets
  • script tags are inserted as they are encountered, and the page is refreshed if the source of an existing script changes for the same data-turbolinks-track-as value
  • look forward to comprehensive documentation for this soon :)

v0.2.3

Changes

• #119 (less JS errors when using Turbograft.Remote, better error behaviour in general when XHR has network-level error)