Skip to content
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

preventScrollReset does not work with fetcher.Form on a redirect in action #9961

Closed
nrako opened this issue Jan 21, 2023 · 2 comments · Fixed by #9963
Closed

preventScrollReset does not work with fetcher.Form on a redirect in action #9961

nrako opened this issue Jan 21, 2023 · 2 comments · Fixed by #9963
Assignees
Labels

Comments

@nrako
Copy link
Contributor

nrako commented Jan 21, 2023

What version of Remix are you using?

1.11.1

Steps to Reproduce

Please check this reproduction case:

https://stackblitz.com/edit/node-sbijvk?file=app/routes/index.tsx

Expected Behavior

<fetcher.Form preventScrollReset method="action"> should not reset the scroll position on a redirect.

Actual Behavior

The scroll position reset on a fetcher.Form.

Since https://stackblitz.com/edit/node-sbijvk?file=app/routes/index.tsx6 a Remix's Form has the preventScrollReset.

@github-actions
Copy link
Contributor

🤖 Hello there,

We just published version 6.7.1-pre.0 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!

@brophdawg11 brophdawg11 added the awaiting release This issue have been fixed and will be released soon label Jan 24, 2023
@github-actions
Copy link
Contributor

🤖 Hello there,

We just published version 6.8.0 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!

@brophdawg11 brophdawg11 removed the awaiting release This issue have been fixed and will be released soon label Jan 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants