This repository has been archived by the owner on Jul 28, 2023. It is now read-only.
🎨 Support CSS in client-side navigations #85
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
23 tasks
DAreRodz
approved these changes
Oct 19, 2022
|
Thanks, David. |
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 support for loading the CSS of the head during the client-side navigations.
I finally opted for not using vDOM diffing, and I also opted for using a
<style>for<link rel="stylesheet">to make sure we do the navigation (body and CSS) in a single step and avoid any FOUC. I think it's simpler this way, but happy to hear other opinions.https://www.loom.com/share/827311414ffd4acdacb2b675b09050fa
@DAreRodz: please check that this solves your problems with CSS during the navigations.