-
Notifications
You must be signed in to change notification settings - Fork 570
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
Works but fails to show the updated value automatically and returns some JS errors in console #571
Comments
UPDATE I have managed to eliminate the 500 error by modifying
to:
I am still getting the |
Is this gem working on Rails 5? |
@victorhazbun Yes it does. |
Hi @acrolink, I'd suggest changing the title of this post to reflect just the Chrome warning message: https://stackoverflow.com/questions/42053775/getting-error-form-submission-canceled-because-the-form-is-not-connected According to the above Stack Overflow, the warning was added in version 56. I'm on 59 now, and still get the message, although the forms aren't broken as reported by users of 56. |
Chrome 66, still getting this issue. |
Chrome 68 here, still getting the "Form submission canceled because the form is not connected" warning in the console. Even though users should never see it, it's annoying. It should be an easy fix: do something like e.preventDefault() on the form submission. |
I have implemented
best_in_place
for a number field inside my Rails app. The inline editing works, it updates the field in the database but fails to show the updated value (i.e. I need to reload the entire page to display the updated value). Moreover, inspecting the Chrome console shows the following:Any idea what might be happening here? Thank you.
The text was updated successfully, but these errors were encountered: