-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Removal of element doesn't really remove element #1028
Comments
Ok found a way to make it work : if you add "fieldRemoveWarn: true, " to the options, the field is actually deleted. |
Are you sure this isn't still a bug? |
Yes it is of course. I'll reopen it. |
@kevinchappell Looks like a critical bug in the latest release. |
Thanks for opening and re-opening this issue. A new version should be released in a few minutes |
## [3.3.1](v3.3.0...v3.3.1) (2020-01-28) ### Bug Fixes * field removed from stage but not formData ([2c6d824](2c6d824)), closes [#1028](#1028)
🎉 This issue has been resolved in version 3.3.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description:
Hi,
When you click on the delete button on an element, it disapears from the DOM (the field is put on "display:none") but is'nt actually removed from the form.
And when you save the data, the field is still in the form. It can easally seen on the demo site under the getData() method.
Environment Details:
Expected Behavior
Field is supposed to be removed from the form
Actual Behavior
Field is just hidden and not removed
Steps to Reproduce
Click a delete button on a field and save data : the field is still here.
screenshot
The text was updated successfully, but these errors were encountered: