-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Save callback should not be executed while the previous wasn't resolved #2539
Comments
Adding to the next iteration, but it'd be good to get some feedback what's the expected behaviour. We can also check some other implementations. |
Just a note that if we ever implement this, we should handle correctly a situation where the first save attempt failed (not sure what was the definition of "completed" above). We should try to continue saving the data again after getting an error/timeout or sth. |
We agreed to handle errors in the separate ticket. In this ticket, we should focus not to execute another save action before the previous one finish. |
Other: Improved call frequency. Closes #9. Closes #10. Closes #12. Closes ckeditor/ckeditor5#1158.
I wrote such a simple sample:
It behaves like this now:
IMO, it should wait with the next "Saving..." until the previous save attempt was completed.
It isn't a big deal if it doesn't wait, but it's odd. It wasn't natural for me.
The text was updated successfully, but these errors were encountered: