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
react-dropzone
I'm mostly curious why this validation exists:
happy-dom/packages/happy-dom/src/nodes/html-input-element/HTMLInputElement.ts
Lines 795 to 802 in e6f9127
And if it can be removed or updated?
I'm using react-dropzone and they have this line https://github.com/react-dropzone/react-dropzone/blob/c36ab5bd8b8fd74e2074290d80e3ecb93d26b014/src/index.js#L807-L808 which triggers and error in vitest + happy-dom
vitest
happy-dom
https://codesandbox.io/p/sandbox/silly-kowalevski-qjrmt6
const fileInput = document.getElementById("my-file"); fileInput.value = null;
doesn't throw errors in any browser
Originally posted by @csantos-nydig in #1495
The text was updated successfully, but these errors were encountered:
fix: [#1604] Consider null as empty string when setting it as value i…
7e28c05
…n HTMLInputElement.value
Related to #1576
Sorry, something went wrong.
9f8f084
…n HTMLInputElement.value (#1606)
Thank you for reporting @csantos-nydig! 🙂
I believe it should be fixed now.
capricorn86
Successfully merging a pull request may close this issue.
I'm mostly curious why this validation exists:
happy-dom/packages/happy-dom/src/nodes/html-input-element/HTMLInputElement.ts
Lines 795 to 802 in e6f9127
And if it can be removed or updated?
Context
I'm using
react-dropzone
and they have this line https://github.com/react-dropzone/react-dropzone/blob/c36ab5bd8b8fd74e2074290d80e3ecb93d26b014/src/index.js#L807-L808which triggers and error in
vitest
+happy-dom
Plain JS example
https://codesandbox.io/p/sandbox/silly-kowalevski-qjrmt6
doesn't throw errors in any browser
Originally posted by @csantos-nydig in #1495
The text was updated successfully, but these errors were encountered: