Fair warning if you end up here - be careful listening to pjax events with Jquery "on". It appears to overwrite the custom pjax event and leaves triggerElement undefined. Probably should be pretty obvious but it took me a while to figure out.
Fair warning if you end up here - be careful listening to pjax events with Jquery "on". It appears to overwrite the custom pjax event and leaves triggerElement undefined. Probably should be pretty obvious but it took me a while to figure out.
`$(document).on("pjax:send", function(e) {
console.log(e.triggerElement) // undefined
})`
Is this worth mentioning in the docs?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #62.
With this PR, you can access the element that triggered the
pjax:sendevent withevent.triggerElement.Fair warning if you end up here - be careful listening to pjax events with Jquery "on". It appears to overwrite the custom pjax event and leaves triggerElement undefined. Probably should be pretty obvious but it took me a while to figure out.
$(document).on("pjax:send", function(e) { console.log(e.triggerElement) // undefined })Is this worth mentioning in the docs?