Fixing of wrong events lifecycle in case when ajax request is not async #72
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
samdark approved these changes Nov 7, 2022
| Would you please add a line for CHANGELOG? |
- updated CHANGELOG.md
| Sure, have added. |
samdark approved these changes Nov 8, 2022
| 👍 |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Fix for case when we use container reloading with synchronous ajax request
$.pjax.reload({container: '#pjax-container', async: false});and events fire in unexpected order:
pjax:beforeSend
pjax:beforeReplace
pjax:success
pjax:complete
pjax:end
pjax:start
pjax:send