Custom selector about instantclick

[pasine]

I have tried to add this feature.
You can see it in my fork.
Since I had to add a new argument to handle the selecor, I prefered to pass everything as an object instead of comma separated paramters.
This would break the actual configuration of the library, that's why I didn't create a pull request.
I think passing parameters as

{mouseover: true, delay: 50, selector : '#foo a'}

will make things much readable, but this is a personal opinion.
With my changes, you can now select which link you want to be preloadable by passing a selector to the init function.

InstantClick.init({ selector : 'a.preload' }); 

[dieulot]

I’m thinking about adding the ability to add data-instant/data-no-instant to a non-link element. That would whitelist/blacklist all links in that element.

In your case, you’d enable whitelisting (InstantClick.init(true)) and then add a data-instant attribute to the element you’re currently using as your selector. That’d solve your problem, right?

[pasine]

Can I ask you why do you prefer to use a data attribute instead of using a javascript selector? Is it for performance or for convenience?

[dieulot]

Convenience for the person new to InstantClick. Allowing two ways to do the same thing would duplicate one’s effort to learn how to set up InstantClick.

The only advantage I see from using selectors over data(-no)-instant on a parent attribute is that you can use classes if you prefer. Not worth the drawback of inhibited learning.

[dieulot]

Blacklisting/Whitelisting all links in one container has landed in 64876dc.