NS_ERROR_ILLEGAL_VALUE:
...{var e=t.state;this._updateBodyAttributes(e.attrs);a.body.innerHTML=e.content;va...

i have included on end of the HTML
`<script src="/js/page-accelerator.min.js</script>

In general terms this library looks like instantclick but more lightweight, so that's good!

I thin that blacklisting links can be improved:

• data-no-pageAccelerator instead of data-pageAccelerator="false". Or something similar. Less characters, more semantic.
• Add ability to blacklisting a group of elements. For example, in instantclick:

To blacklist all links in a parent element, add data-no-instant to that element.

I added the script to the bottom of my site and called pageAccelerator();.
Everytime I click a link I get this error:

pageAccelerator.js:formatted:48Uncaught (in promise) TypeError: t.on is not a function(...)
     _updateHistory               @ pageAccelerator.js:formatted:48
    (anonymous function)     @ pageAccelerator.js:formatted:84

Which I think refers to https://github.com/Easyfood/pageAccelerator/blob/master/src/page-accelerator.js#L37

The last update date was 10 days ago.

It seems that pageAccelerator cannot be used with browserify.

The following code fails:

// client.js
var pageAccelerator = require('page-accelerator')

pageAccelerator(function(err, res) {
    console.log('page loaded', err, res)
})

error message:

    TypeError: pageAccelerator is not a function

Would you consider to add compatibility with browserify? This would ease build processes, by not having to explicitely copy the dist/page-accelerator.min.js to a suitable location.

On IE11 it does not work, simply because there is no window.Promise.
I wonder why you list it as working on IE 10 because there is no window.Promise either

Currently, there's only one test, testing the browser global functionality of the module. There are absolutely no tests written for the CommonJS or AMD modules.

t.href is empty.

I use custombox.js modal in my page and it uses ID and href=#id to show modal on page, seems it has conflict between these addressing in URL, cause it stop page to show content correctly

Why JQuery plugins don't work?

After adding this to my Hexo blog, can't go back in Chrome.

Error message:

Uncaught TypeError: e.body.attr is not a function

After trying adding this to my WP site:

• WonderPlugin Slider is not displayed after pajax-ing
• Cannot go back, go forward (in Chrome Browser menu)

Info:
Chrome 53.0.2785.116 (64-bit) on Mac OS
WordPress 4.6

The global object in a browser window is window, which can also be referenced using this, like I said in my previous comment in #6 when writing a tip about how to implement this library as a universal module. However, in the module factory block, the global object is referenced by window, which, when loaded as a CommonJS module is undefined. This causes an error, and prevents the user from using this library.

Attaching screenshot:

FYI @EvandroLG

The accelerator is avoiding user to open links into another window or tab.

This can be replicated simply by clicking into a link holding CONTROL (M$ Windows or Linux) or COMMAND (Mac).

The expected behaviour is that link must be opened into a new window or tab. The accelerator must not intercept the link if the proper keys are holded.

Hi, a demo would have been great to show lib capabilities :)