-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[fix] use defaults when no opts passed to router #2819
Conversation
🦋 Changeset detectedLatest commit: e1bdb00 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for getting to this. I have a question below but otherwise it's an approval from me.
Co-authored-by: Bjorn Lu <34116392+bluwy@users.noreply.github.com>
I've re-run the tests twice but it seems like a fluke consistently happening recently. It's likely the way we detect scrolls that's causing it but this change should be safe as is. Merging this to fix #2853 |
* [fix] revert #2819 and add code comment * lint * Update packages/kit/src/runtime/client/renderer.js Co-authored-by: Bjorn Lu <34116392+bluwy@users.noreply.github.com> * reverse condition Co-authored-by: Rich Harris <richard.a.harris@gmail.com> Co-authored-by: Bjorn Lu <34116392+bluwy@users.noreply.github.com>
I noticed this in another code review
There are somethings we don't do when
!opts
. E.g. we don't do thedocument.body.focus();
. I have no idea why this would be and it seems wrong