This repository was archived by the owner on Jul 28, 2023. It is now read-only.
Add client-side navigation support for wp-ignore directive#163
Merged
DAreRodz merged 3 commits intomain-wp-directives-pluginfrom Mar 3, 2023
Merged
Add client-side navigation support for wp-ignore directive#163DAreRodz merged 3 commits intomain-wp-directives-pluginfrom
wp-ignore directive#163DAreRodz merged 3 commits intomain-wp-directives-pluginfrom
Conversation
23 tasks
6 tasks
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
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.
What
Allows elements with the
wp-ignoredirective to keep their content afternavigatecalls.Why
During navigations, the content inside elements with
wp-ignorecould change, and those updates should not be reflected (those parts of the HTML document should be ignored).How
Implementing the
ignoredirective in a way that:dangerouslySetInnerHTMLprop never changes.