smoothState.js
smoothState.js is a jQuery plugin that progressively enhances page loads to give us control over page transitions. If the user's browser doesn't have the required features, smoothState.js fades into the background and never runs.
Built with smoothState.js
Below are some cool sites built with smoothState.js. Feel free to submit a pull request with your own site, or tweet me with a link.
Contributor demos
Live Sites
- Twitch Conf by Alexis Gallisá
- Interactive portfolio by Recardo Zanutta
- Refune by Victor Meyer
- Beau Han Xu London by Lawrence Gosset
- Rock Werchter by Rock Werchter
- Portfolio Site by Aaron Porter
- Open Innovation in Science by Roland Schütz
Need help?
If you need a little help implementing smoothState there are a couple things you could do to get some support:
- Post on stackoverflow using the smoothState.js tag.
- Join the Gitter room and talk to some of the contributors.
- Contact Miguel directly, he provides pair-programing help billed by the hour
Please avoid creating a Github issue with personal support requests, to keep the tracker clear for bugs and pull requests.
Intro
Imagine, for a second, how disorienting it would be if touching a doorknob teleported you to the other side of the door. Navigating the web feels like using a teleporting doorknob. Layouts change, elements rearrange or disappear, and it takes time for the user to adjust. Smooth transitions reduce the effort it takes for users to get settled into a new environment.
Javascript SPA frameworks, sometimes referred to as MVC frameworks, are a common way to solve this issue. These frameworks often lose the benefits of unobtrusive code. Writing unobtrusive javascript gives us more resilience to errors, and improved performance and accessibility.
How does smoothState.js work?
smoothState.js provides hooks that can be used to choreograph how elements enter and exit the page during navigation. It uses the time the animations are running to fetch content via AJAX to inject into the page.
smoothState.js doesn't dictate how things on the page should be animated. It supports CSS animations, as well as JS animation libraries like velocity.js.
Design philosophy and requirements
The project's main goal is to allow developers to add page transitions without having to add any logic to the backend. We keep things unobtrusive at all times.
smoothState.js initializes on containers, not links. Think of a container as a small window object embedded in the page.
- Every URL on your site should return a full layout - not just an HTML fragment
- The smoothState container needs to have an
id
set - a unique hook to tell us what to update on the page - All links and forms on the page should live within the container
These requirements makes the website resilient, since it smoothState.js can abort and simply redirect the user if an error occurs. Making each link return a full page also ensures that pages are created with progressive enhancement in mind.
Getting started
All we need to do to get started is:
- Include a copy of jQuery and jQuery.smoothState.js on your page
- Add a container with an id of
#main
and include some links inside of it - Create a new js file and run
$('#main').smoothState()
$(function() {
$('#main').smoothState();
});
By default, smoothState.js will:
- Prevent links and forms from triggering a full page load, if possible
- Use AJAX to request pages and replace the content appropriately
- Update URLs and browsing history so that browsing expectations aren't broken
smoothState.js will not add page transitions to pages. You'll need to define the animations you want to run using the hooks smoothState.js provides.
onBefore
- Runs before a page load has been startedonStart
- Runs once a page load has been activatedonProgress
- Runs if the page request is still pending and theonStart
animations have finishedonReady
- Run once the requested content is ready to be injected into the page and the previous animations have finishedonAfter
- Runs after the new content has been injected into the page and all animations are complete
Options
smoothState.js provides some options that allow customization of the plugin's functionality. The default options are overridden by passing an object into the smoothState
function.
Options example
$(function(){
'use strict';
var options = {
prefetch: true,
cacheLength: 2,
onStart: {
duration: 250, // Duration of our animation
render: function ($container) {
// Add your CSS animation reversing class
$container.addClass('is-exiting');
// Restart your animation
smoothState.restartCSSAnimations();
}
},
onReady: {
duration: 0,
render: function ($container, $newContent) {
// Remove your CSS animation reversing class
$container.removeClass('is-exiting');
// Inject the new content
$container.html($newContent);
}
}
},
smoothState = $('#main').smoothState(options).data('smoothState');
});
debug
If set to true
, smoothState.js will log useful debug information to the console, instead of aborting. For example, instead of redirecting the user to a page on an error, it might log:
No element with an id of “#main” in response from “/about.html”.
// Default
$('#main').smoothState({ debug: false });
anchors
A jQuery selector specifying which anchors within the smoothState
element should be bound.
// Default
$('#main').smoothState({ anchors: 'a' });
hrefRegex
A regular expression to specify which anchor with a specific href property based on the regex smoothState should bind to. If empty, every href will be permitted.
// Default
$('#main').smoothState({ hrefRegex: '' });
forms
A jQuery selector specifying which forms within the smoothState
element should be bound.
// Default
$('#main').smoothState({ forms: 'form' });
allowFormCaching
Controls whether or not form submission responses are preserved in the cache. If set to true, smoothState will store form responses in the cache. This should be set to false unless you understand how caching form results will affect your website's behaviour very well.
// Default
$('#main').smoothState({ allowFormCaching: false });
repeatDelay
The minimum number of milliseconds between click/submit events. User events ignored beyond this rate are ignored. This can be used to ignore double-clicks so that the user's browser history won't become cluttered by incompleted page loads.
// Default
$('#main').smoothState({ repeatDelay: 500 });
blacklist
A jQuery selector specifying which elements within the smoothState
element should be ignored. This includes both form and anchor elements.
// Default
$('#main').smoothState({ blacklist: '.no-smoothState' });
prefetch
There is a 200ms to 300ms delay between the time that a user hovers over a link and the time they click it. On touch screens, the delay between the touchstart
and touchend
is even greater. If the prefetch
option is set to true
, smoothState.js will begin to preload the contents of the URL during that delay. This technique will increase the perceived performance of the site.
// Default
$('#main').smoothState({ prefetch: false });
prefetchOn
The name of the events to listen to from anchors when prefetching.
// Default
$('#main').smoothState({ prefetchOn: 'mouseover touchstart' });
If you would like to throttle the prefetch, do so by firing custom events.
Libraries like @tristen's hoverintent can be used to throttle prefetching based on the user's intent, by triggering a custom intent
event. To use it with smoothState.js, set intent
as the prefetchOn
option.
$('#main').smoothState({ prefetchOn: 'intent' });
Or, for the opposite effect, use something like @cihadturhan's jQuery.aim and add spider sense-like prefetching to smoothState.js.
$('#main').smoothState({ prefetchOn: 'aim' });
locationHeader
A field name to lookup among the headers from the HTTP response to alert smoothState.js of any redirected URL.
smoothState.js makes AJAX requests using XMLHttpRequest
, which silently follows redirects. This transparence prevents smoothState.js from knowing if a request resulted in a redirection.
For example, when you visit /about
and the server redirects you to /about/company
, smoothState.js is only ever informed of a successful response from /about
. The locationHeader
option gives smoothState.js a HTTP response header to consult and replace the browser's history entry with the real URI.
$('#main').smoothState({ locationHeader: 'X-SmoothState-Location' });
cacheLength
The number of pages to cache. smoothState.js can cache pages in memory, avoiding the user having to request pages more than once. Cached pages will load instantaneously.
// Default
$('#main').smoothState({ cacheLength: 0 });
loadingClass
The class to apply to the body
while a page is still loading, unless the page is received before the animations are complete.
// Default
$('#main').smoothState({ loadingClass: 'is-loading' });
scroll
Scroll to top after onStart and scroll to hash after onReady. This is default behavior, if you want to implement your own scroll behavior, set scroll: false
// Default
$('#main').smoothState({ scroll: true });
alterRequest
A function to alter a request's AJAX settings before it is called. This can be used to alter the requested URL, for example.
// Default
$('#main').smoothState({
// Param `request` is an `Object` that is currently set to be used
alterRequest: function(request) {
// Must return and `Object` that will be used to make the request
return request;
}
});
alterChangeState
A function to alter a history entry's state object before it is modified or added to the browser's history. This can be used to attach serializable data to the history entry, for example.
// Default
$('#main').smoothState({
// Param `state` is an `Object` that contains the container ID, by default
alterChangeState: function(state) {
// Must return a serializable `Object` that is associated with the history entry
return state;
}
});
onBefore
The function to run before a page load is started.
// Default
$('#main').smoothState({
// `$currentTarget` is a `jQuery Object` of the element, anchor or form, that triggered the load
// `$container` is a `jQuery Object` of the the current smoothState container
onBefore: function($currentTarget, $container) {}
});
onStart
The function to run once a page load has been activated. This is an ideal time to animate elements that exit the page and set up for a loading state.
// Default
$('#main').smoothState({
onStart: {
// How long this animation takes
duration: 0,
// A function that dictates the animations that take place
render: function ($container) {}
}
});
onProgress
The function to run only if the page request is still pending and onStart
has finished animating. This is a good place to add something like a loading indicator.
// Default
$('#main').smoothState({
onProgress: {
// How long this animation takes
duration: 0,
// A function that dictates the animations that take place
render: function ($container) {}
}
});
onReady
The function to run when the requested content is ready to be injected into the page. This is when the page's contents should be updated.
// Default
$('#main').smoothState({
onReady: {
duration: 0,
// `$container` is a `jQuery Object` of the the current smoothState container
// `$newContent` is a `jQuery Object` of the HTML that should replace the existing container's HTML.
render: function ($container, $newContent) {
// Update the HTML on the page
$container.html($newContent);
}
}
});
onAfter
The function to run when the new content has been injected into the page and all animations are complete. This is when to re-initialize any plugins needed by the page.
// Default
$('#main').smoothState({
onAfter: function($container, $newContent) {}
});
Methods and properties
smoothState
provides some methods and properties, made accessible through the element's data
property.
// Access smoothState
var smoothState = $('#main').smoothState().data('smoothState');
// Run method
smoothState.load('/newPage.html');
Properties
href
The URL of the content that is currently displayed.
cache
An object containing the cached pages after they are requested.
Methods
load(url)
This loads the contents of a URL into our container.
fetch(url)
This fetches the contents of a URL and caches it.
clear(url)
This clears a given page from the cache. If no URL is provided it will clear the entire cache.
restartCSSAnimations()
This restarts any CSS animations applying to elements within the smoothState
container.
FAQ
Help! My
$(document).ready()
plugins work fine when I refresh but break on the second page load.
smoothState.js provides the onAfter
callback function that allows you to re-run your plugins. This can be tricky if you're unfamiliar with how AJAX works.
When you run a plugin on $(document).ready()
, it's going to register only on elements that are currently on the page. Since we're injecting new elements every load, we need to run the plugins again, scoping it to just the new stuff.
A good way to do this is to wrap your plugin initializations in a function that we call on both $.fn.ready()
and onAfter
. You'll want to specify the context each time you initialize the plugins so that you don't double-bind them. This is called a "module execution controller".
Contribute
We're always looking for:
- Bug reports, especially those for aspects with a reduced test case
- Pull requests for features, spelling errors, clarifications, etc.
- Ideas for enhancements
- Demos and links to sites built with smoothState.js
How to integrate SmoothState with Wordpress at all?
There are few problems with that.
There is one of you that have a complete and serious guide?
For example: I use in my Wordpress both "Visualizer" plugin (that visualize Google Charts in my pages) and "DataTables" plugin of jQuery.
Both aren't working when I use SmoothState.
When I call a page in wordpress that contain one of these from my home page nothing works. The page is blank. Without code. If I refresh browser on that page then everything works.
I suppose the problem is with ajax call of the plugins, but I'll never find a solution. That's why I'm here asking you...
HOW TO?
Update DOM elements outside of $container
smoothState.js version tested:
Description
On the website I'm building now I have information attached to
<body>
such asid
,classes
andstyles
. Like below:<body id="project-name" class="project single theme-dark" style="background:white">
..in order to control the page's:
I initialize smoothState on a div #main and when I click a link everything under #main gets updated. The problem is that
body
not gets updated.Possible solution:
My first approach to fix this was to use the callback
onEnd
, but none of the variables passed to therender
function (url, $container, $content
) holds any information about the<body>
. At least to my knowledge – am I missing something?Since I couldn't solve this with the callback functions I made changes to jquery.smoothState.js. What I did was to extend the
storePageIn
function, adding information to the object variable with a new keymeta
. See code below:..and then I also extended the function
updateContent
to actually updatebody
:Discussion
meta information
about the page being fetched like I suggested above?Integrate SmoothState with Wordpress at all.
I opened a new space blank and clean here:
http://ginolon.altervista.org
I've put here Wordpress 3.9.1 and followed this guide: http://www.parsonsprojects.co.uk/smoothstate-wordpress/
I've changed every "$" to "jQuery" because of a lot of errors.
Everything works except some plugins like "Visualizer" and "Inline Google Spreadsheet" that work only if I open the page that contain them or if I refresh the page (you can try now in the live site).
After this I followed the guide of @miguel-perez to fix this issue, that you can find it here: https://github.com/weblinc/jquery.smoothState.js/issues/64#issuecomment-54657406, without success.
I have an error:
"Uncaught TypeError: Cannot read property 'apply' of undefined"
You can try from yourself on the live site.
The question is: HOW TO? Where I'm doing wrong?
[FEATURE] Replace meta and link tags
This update replaces meta and link tags of the active document if its "body"-content is replaced by the cached "body"-content.
There are to new default options for this, metaTags and linkTags. So you can define your own tags.
What do you think about this?
Just have to say, this is awesome! But the title is not updating correctly in Chrome (v 36.0.1985.143). Instead of the given title-tag it sets the url (this is the correct url though) as the title. Any ideas?
Works perfect in Firefox and Safari.
Clunky transitions on slow connection speeds
My client is experiencing very clunky transitions on page loads. I suspect this is a caching issue, so I am wondering if there you have a suggestion for how we could remedy this. I see there is a caching option in the documentation, so I am wondering if this will help remedy this issue. You can see the site in question at: http://bobby.gramacy.com/
Automatic Google Analytics Integration
I think it would be great if Google Analytics would automatically be tiggered if available.
So adding something like this:
Redrawing of element creates flickering
smoothState.js version tested:
Browser versions or Packager version tested against:
Description:
The result that was expected:
The result that occurs instead:
Why is the redraw needed?
Thanks, Roland
smoothState and slick not working
If i use smoothState and Slick slider together, i take that error
It happens when I'm doing some switching between pages.
Sorry for my english, how fix it?
My JS code
Cross - Browser Problem
First of all: Great idea and great script, but i am experiencing issues with browsers other than Chrome.
In Firefox the following happens:
In Safari / Webkit the animations do not trigger at all (this may be for me being a noob).
System is OS X 10.9.4 with Chrome 36, Firefox 31, Safari 7.0.6
Sorry if those issues are my failure.
Foundation plugins and smoothState.js
Hi there, I am using the foundation framework and want to use smoothState.js. Does anybody know how to re-initialize foundation plugins with smoothstate.js? They only work if I hit browser refresh. All the other jQuery plugins seem to work - just foundation is giving me a headache... I think an example/demo would be really helpful, maybe the same for the other famous css framework Bootstrap?
I tried this:
Adding Plugins After Page Load http://foundation.zurb.com/sites/docs/javascript.html#adding-plugins-after-page-load
and this:
Adding Content to Plugins http://foundation.zurb.com/sites/docs/javascript.html#adding-content-to-plugins
...without success. I guess I just don't really when to use onAfter and onReady? And then I was given the link by @miguel-perez but I also do not understand how to include that. https://gist.github.com/miguel-perez/476046a42d229251fec3
thank you!