Refresh back button for chrome 136 #39565
Merged
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
Closes keycloak#39540 Signed-off-by: rmartinc <[email protected]>
jonkoops
approved these changes
May 8, 2025
ahus1
approved these changes
May 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Closes #39540
Since 136 chrome does not respect
cache-control: no-storeanymore (see issue). The pages are cached anyway. It seems that chrome checks now cookies (and other things) to decide if the page can be cached or not by default. There is also an API to specify what changes (cookies, storage entries,...) triggers the the eviction of the cache (but it's not standard). For the moment the PR changes the tests to do a refresh when needed for the back. It's only added for chrome by now (maybe other browsers will follow this idea).