This repository has been archived by the owner on Jul 28, 2023. It is now read-only.
馃帹 Add meta tag to opt-in to client-side navigations #86
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
This was referenced Oct 19, 2022
SantosGuillamot
approved these changes
Oct 20, 2022
|
Thanks, Mario! |
luisherranz
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I've added a mechanism to opt-in to client-side navigations using a metatag, so navigation can do a fallback after receiving the HTML of a page that is not client-side navigation friendly.
I left them activated by default for now, although I want to add an admin screen to toggle them on and off.
https://www.loom.com/share/32bfdeb904e04c7e933474744e11be81