perf(livewire): enable the back button cache #2044
Merged
Conversation
This file contains 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
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.
Fixes a performance regression introduced in V4.
Currently, the notification icon component is disabling the browser back/forward navigation cache due to a Livewire config setting. In other words, when pressing the back button (or, more probably, backswiping on mobile), the entire page must be re-requested even if nothing has changed. This ultimately results in more calls to the server, and those additional calls are often unnecessary.
This config change results in Livewire allowing the back/forward cache to be used again.
Unfortunately, there isn't a great way to test this PR locally because the local websocket listening for changes in order to trigger an auto-refresh also disables the bfcache.