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
handleTaggedFormSubmitEvent
Self-hosting
When you assign plausible-event-name to a <form>, the Plausible JS will RE-SUBMIT THE FORM. This behavior is completely undocumented.
plausible-event-name
<form>
This will cause a controlled form (ie. in a React app) to be re-submitted, even if I didn't want it to be submitted.
I'm honestly shocked somebody thought this was a good idea.
First, the handler should check event.defaultPrevented BEFORE attempting to defaultPrevent itself and then re-submit.
event.defaultPrevented
Second, the documentation should show a massive red warning with why you should not use this on a controlled <form>.
No response
- OS: all - Browser: all - Browser Version: all Likely affects Plausible Cloud.
The text was updated successfully, but these errors were encountered:
Thanks you for the bug report @shahyar!
Your tone, however, is unacceptable. If you cannot stay respectful you will not be allowed to participate in any future discussions.
Sorry, something went wrong.
No branches or pull requests
Past Issues Searched
Issue is a Bug Report
Using official Plausible Cloud hosting or self-hosting?
Self-hosting
Describe the bug
When you assign
plausible-event-name
to a<form>
, the Plausible JS will RE-SUBMIT THE FORM. This behavior is completely undocumented.This will cause a controlled form (ie. in a React app) to be re-submitted, even if I didn't want it to be submitted.
I'm honestly shocked somebody thought this was a good idea.
Expected behavior
First, the handler should check
event.defaultPrevented
BEFORE attempting to defaultPrevent itself and then re-submit.Second, the documentation should show a massive red warning with why you should not use this on a controlled
<form>
.Screenshots
No response
Environment
The text was updated successfully, but these errors were encountered: