You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you inspect the console for the cart, in the Edit Item area (in the cart modal) or the Add to Cart (on product page) before you take any action, you will see the error below in the form action. This error is being caused by the file, edit-item-quantity-button.tsx or in the Add to Cart component. This error with Forms is discussed here in this issue: vercel/next.js#56234. The form action still works on submit, so maybe this is a "false" error of sorts and can be safely ignored? Or maybe there is some code that can be fixed to prevent this error? The strange thing is that the SubmitButton uses e.preventDefault(), so not sure why the form is firing in React on page load. It does seem to be some bug related to useFormStatus.
javascript:thrownewError('A React form was unexpectedly submitted. If you called form.submit() manually, consider using form.requestSubmit() instead. If you\'re trying to use event.stopPropagation() in a submit event handler, consider also calling event.preventDefault().')
The text was updated successfully, but these errors were encountered:
If you inspect the console for the cart, in the Edit Item area (in the cart modal) or the Add to Cart (on product page) before you take any action, you will see the error below in the form action. This error is being caused by the file, edit-item-quantity-button.tsx or in the Add to Cart component. This error with Forms is discussed here in this issue: vercel/next.js#56234. The form action still works on submit, so maybe this is a "false" error of sorts and can be safely ignored? Or maybe there is some code that can be fixed to prevent this error? The strange thing is that the SubmitButton uses e.preventDefault(), so not sure why the form is firing in React on page load. It does seem to be some bug related to useFormStatus.
The text was updated successfully, but these errors were encountered: