Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
hijack links for pushState in Backbone
// All navigation that is relative should be passed through the navigate
// method, to be processed by the router. If the link has a `data-bypass`
// attribute, bypass the delegation completely.
$(document).on("click", "a[href]:not([data-bypass])", function(evt) {
// Get the absolute anchor href.
var href = { prop: $(this).prop("href"), attr: $(this).attr("href") };
// Get the absolute root.
var root = location.protocol + "//" + location.host + Application.root;
// Ensure the root is part of the anchor href, meaning it's relative.
if (href.prop.slice(0, root.length) === root) {
// Stop the default event to ensure the link will not cause a page
// refresh.
evt.preventDefault();
// Note by using Backbone.history.navigate, router events will not be
// triggered. If this is a problem, change this to navigate on your
// router.
Backbone.history.navigate(href, true);
}
});
@tbranyen
Copy link
Author

tbranyen commented Mar 27, 2015

GitHub never notified me of any of these comments >_> I just updated the Gist to latest version I've been using.

@luca-moser
Copy link

luca-moser commented Apr 3, 2015

Shouldn't it be href.attr in the navigate function?

@jaapz
Copy link

jaapz commented Jun 18, 2015

@XemsDoom yes it should

You also should probably add a check whether or not someone called preventDefault on the event.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment