Publish packages 🚀#940
Open
lemonmade wants to merge 1 commit into
Open
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@quilted/preact-router@0.4.0
Minor Changes
#939
908f1adThanks @lemonmade! - Added automatic scroll restoration toNavigationIn a single-page app the browser's native scroll restoration is unreliable: on a back/forward navigation it restores the scroll offset against the document as it exists at
popstatetime, but an async route hasn't rendered its content yet, so it restores against the wrong (usually shorter) document and lands at the wrong offset. Forward navigations are also frequently left at the previous page's offset instead of the top.Navigationnow owns scroll restoration. In the browser it switcheshistory.scrollRestorationto'manual'and keeps its own per-entry scroll offsets, keyed by navigation id and persisted tosessionStorage(so they survive a reload within the tab session):Offsets that need the destination route's content committed (a restore or a hash target) are applied on the next animation frame; a plain reset to the top is applied synchronously to avoid a flash of the new route at the previous offset.
This is enabled by default. Pass
scrollRestoration: falseto leave scrolling entirely to the browser/your app:@quilted/preact-localize@0.4.4
Patch Changes
908f1ad]:@quilted/quilt@0.9.7
Patch Changes
908f1ad]: