progressive-pushstate

Allow pushstate/popstate support using a progressive-enhancement design pattern.

Why Use This Library

- You want the state of a web page to be rendered by both the client and the server side.
- You want the state of a web page to be controlled by the page's query string.
- You want to make sure that make sure your page's state can be shared correctly via email/social media/etc.
- You want all of the above but you don't want to be tied into any specific framework (e.g. React, jQuery, Angular, etc)
- You want all of the above implemented using progressive enhancement to ensure older browser's that don't support the library will still be able to use your application.

Note that library allows the developer to not worry about browser history and back/forward button usage -- as long as s/he has set up the library correctly, everything should just work automatically (more on this later).

What it is not

- This is not a library that will include a whole bunch of page state visual effects for free. You must know JavaScript and be able to implement these yourself.
- It will not run JavaScript on the server side.

How to Use it.

$3

Let's assume you page has a bunch of links like this:

``
Customer Support
`

This link currently works like you would expect it to (by going to the server and fetching the relevant page), but now you want to be clever and have this link trigger an AJAX request that will only retrieve the HTML fragment of the page that is different from the original page (i.e. the content of the page without the header and footer).

* First, add the progressive-pushstate script to the bottom of your page.

`



`

* Next, just add the pp-link class to the page:

`
Customer Support
`

* Finally create the javascript logic in a separate JavaScript file. You first need to ensure that you register the JavaScript function that will be triggered when a pp-link is clicked:

`
pp.init(popstateEvent);
`

Then you must implement the popstate event:

`
function popstateEvent(e) {
// insert logic here

...
};
`

Note that e will have a state property that will be an object containing the parsed query string of the link that was clicked. For example, if the URL clicked was /path/to/page?section=support&level=2, then the state object would be set to

`
{
section: "support",
level: "2"
}
`

The developer should have enough information to replicate the server side behavior on the client side.

If the URL contains a hash tag, then that information is stored in the state object under the property _ppHash. For example, if the URL /path/to/page?section=support&level=2#question2 was clicked, the state object would be set to:

`
{
section: "support",
level: "2"
_ppHash: "question2"
}
`

To ensure that your application maintains a progressively-enhanced design pattern, it is recommended to use hash tags only for the purpose of anchoring to a particular section to a page, since hash tags are never passed to the server (see section 4.1 of RFC 2396, "Uniform Resource Identifiers (URI)").

A great example of how this works is in the desktop menu of this example page




$3

Let's assume you page has a form that looks like this:

`



placeholder="Your full name (first, middle and last)." />
placeholder="The country you live in."/>




`

This form currently works like you expect it to (by giving the form data to the server and fetching a result page), but now you want to be clever and have a form submit trigger an AJAX request that will only retrieve the HTML fragment of the page that is different from the original page (i.e. the content of the page without the header and footer).

* First, just as before, add the progressive-pushstate script to the bottom of your page.

`



`

* Next, just add the pp-form class to the form you want this AJAX magic to happen with. You should also put all events in the form that can trigger an ajax request inside the data-pp-events attribute:

`



placeholder="Your full name (first, middle and last)." />
placeholder="The country you live in."/>




`

* Creating the Javascript logic for the form is about the same as the link scenerio. You first need to ensure that you register the JavaScript function that will be triggered when a pp-link is clicked:

`
pp.init(popstateEvent);
`

Then you must implement the popstate event:

`
function popstateEvent(e) {
// insert logic here

...
};
`

Note that e will have a state property that will be an object containing the parsed query string of the form that was clicked. For example, if we filled the form above with "Zoltan" as the name and "Canada" as the country, then the state object would be set to

`
{
name: "Zoltan K. Hawryluk",
country: "Canada",
submitButton: "Submit My Country"
}
`

The developer should have enough information to replicate the server side behavior on the client side.




Initialization Options

The pp.init() method can take an optional second parameter, which is a JavaScript oject containing a list of options. For example:


`
pp.init(popstateEvent, {
doPopstateOnload: true
});
`

will execute the popstateEvent function when the page loads. This can be used, for example, if you decide not to implement any server side logic to render state on page load, but still like the idea of using the query string to control state.

The properties of the options object include:

- doPopstateOnload: fire the popstateEvent onload (default: true)
- defaultState: the initial default state of the application (default: {} or if a link with class "pp-default" exists, the URL of that link).
- pushScrollState: (experimental) enables the application to keep track of scrollbar position in the app. (default: false)
- debounceTime: (experimental) sets the debounce time for resize and scroll events default: 50)
- keyDebounceTime: sets the debounce time for form key* and input events (default: 500)
- collapseMulti: If a form element name can have multiple values submitted at once (e.g. radio buttons), this allows the values to be submitted into one variable (e.g. sortBy=name,age,phoneNumber) instead of the usual expanded way a form usually send them (e.g. sortBy=name&sortBy=age&sortBy=phoneNumber).

Runtime Options

- If a pp-link link has a class pp-merge, then the data in the link will merge with the current value inside window.history.state. This will, of course, also be reflected in the URL.
- Similarly if a pp-form has a class pp-merge, then the data in the form will merge with the current value inside window.history.state.

Examples

* hybrid mobile/desktop menu using both links and a select dropdown
* search as you type example
* table filtering example




Dependencies

None. This is plain ol' JavaScript, my friend. You can use it with jQuery/Moo Tools/Dojo/etc., but you don't need to.

Browser Support

This has been tested on the latest versions of Firefox, Safari, Opera and Chrome as well as Internet Explorer 10+. Any browser that supports the HTML5 Session Management API should support this library.

It should work with the history.js HTML5 Session Management API polyfill, but this hasn't been tested. We may be doing so in the future, but since this progressive-pushstate.js was build with progressive enhancement in mind, it was not our main focus (especially since, if a dev uses this library correctly, any application that uses it should work with the Session Management API, because it was coded with progressive enhancement in mind).

More Information

I have written a fairly detailed blog post about this library on my blog, User Agent Man

Other Notes

This document uses the word "we" a lot (especially in this paragraph). The only person it really refers to at the moment is Zoltan Hawryluk, since we want to make sure we are not speaking on anyone else's behalf. However, it must be noted this libary does include code (formData2QueryString`) originally written by Matthew Eernisse in March 2005 with bugfixes by Mark Pruett and multi-select support added by Craig Anderson (HTML5 form element support was added by Zoltan for this script). We have never met these other developers, but they have done some great work. Since this function is released under the Apache License, I have done the same for this whole library.

We also want to make sure to mention that we encourage other folks to contribute/add/refactor/change this code as they see fit. Please send us a pull request, and we'll see if we can make Zoltan's "we" into more of a community "we". :-)

License

This library is licensed under the Apache License, Version 2.0 (the "License"). More info at: http://www.apache.org/licenses/LICENSE-2.0