var pjax = new Pjax({
selectors: ['#pjax-container'],
cacheBust: false
});
In this case events fired
complete event fired
success event fierd
But
pjax.options.requestOptions = pjax.options.requestOptions || {};
pjax.loadUrl(url, pjax.options);
In this case event fired
complete event fired
Is this flow right?
or Did I made a mistake?
Thx.
**My code**
var pjax = new Pjax({
selectors: ['#pjax-container'],
cacheBust: false
});
In this case events fired
1. complete event fired
2. success event fierd
But
pjax.options.requestOptions = pjax.options.requestOptions || {};
pjax.loadUrl(url, pjax.options);
In this case event fired
1. complete event fired
Is this flow right?
or Did I made a mistake?
Thx.
Have you checked to see if pjax:error is being fired instead? Pjax always triggers either pjax:sucess or pjax:error when triggering pjax:complete.
Have you checked to see if `pjax:error` is being fired instead? Pjax always triggers either `pjax:sucess` or `pjax:error` when triggering `pjax:complete`.
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.
My code
var pjax = new Pjax({
selectors: ['#pjax-container'],
cacheBust: false
});
In this case events fired
But
pjax.options.requestOptions = pjax.options.requestOptions || {};
pjax.loadUrl(url, pjax.options);
In this case event fired
Is this flow right?
or Did I made a mistake?
Thx.
Have you checked to see if
pjax:erroris being fired instead? Pjax always triggers eitherpjax:sucessorpjax:errorwhen triggeringpjax:complete.@venzersiz Are you still having this issue?
@BehindTheMath I'll check again.
@BehindTheMath Oh, I made a mistake. The cause was jQuery pjax I've used has same name event handler. There isn't the problem.