We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
<input type="reset" />
Using <input type="reset" /> on a form with hardcoded values clears the form when it shouldn't.
value
https://github.com/angrytongan/use-enhance-bug
git clone https://github.com/angrytongan/use-enhance-bug npm install npm run dev
Browse to http://localhost:5173/reset
Press Reset.
Form is reset, but values shouldn't not change. See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/reset
No response
System: OS: macOS 12.6.2 CPU: (4) x64 Intel(R) Core(TM) i3-1000NG4 CPU @ 1.10GHz Memory: 272.98 MB / 8.00 GB Shell: 5.8.1 - /bin/zsh Binaries: Node: 18.7.0 - ~/.nvm/versions/node/v18.7.0/bin/node Yarn: 1.22.19 - /usr/local/bin/yarn npm: 8.15.0 - ~/.nvm/versions/node/v18.7.0/bin/npm Browsers: Chrome: 109.0.5414.87 Safari: 16.2 npmPackages: @sveltejs/adapter-auto: ^1.0.0 => 1.0.0 @sveltejs/kit: ^1.0.0 => 1.0.7 svelte: ^3.54.0 => 3.55.0 vite: ^4.0.0 => 4.0.4
annoyance
Related to #8513 via #8404.
The text was updated successfully, but these errors were encountered:
BTW...
Sorry, something went wrong.
Might be worth moving this to the sveltejs/svelte repository. It’s an issue related to Svelte itself rather than SvelteKit.
Moved to sveltejs/svelte#8220
No branches or pull requests
Describe the bug
Using
<input type="reset" />
on a form with hardcodedvalue
s clears the form when it shouldn't.Reproduction
https://github.com/angrytongan/use-enhance-bug
Browse to http://localhost:5173/reset
Press Reset.
Form is reset, but values shouldn't
notchange. See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/resetLogs
No response
System Info
Severity
annoyance
Additional Information
Related to #8513 via #8404.
The text was updated successfully, but these errors were encountered: