Optimize bespoke template for bfcache #323
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
This was referenced Mar 14, 2021
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.
Back/forward cache (a.k.a bfcache) is the browser optimization for enabling instant back and forward navigation. Firefox and Safari have enabled while a long time, and recently it has added to Chrome for mobile.
Marp CLI's bespoke template has disabled bfcache by adding
unloadevent. So I refactored some bespoke plugins to use new Page Lifecycle API. A notable change is in sync plugin: Persist sync key between navigation, through history state instead of URL query parameter.By this change, the slide HTML can get a 100% Lighthouse Best Practice score.