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
When typing in zen mode, it saves automatically, I guess it's supposed to save just once (per change) but it constantly tries to save the same thing again and again (even when you have made no changes after once) with a lot of POST requests which seems never ending in an infinite loop
The text was updated successfully, but these errors were encountered:
AwesomeStickz
changed the title
Zen mode doesn't save just once but constantly tries to save your translation
Zen mode doesn't just save once per change but constantly tries to save same change again and again
Feb 12, 2022
The saving is supposed to happen on the change event, which should happen only when the textarea loses focus. Maybe you have some browser extension that causes this event to trigger more often?
Though this is now fixed and closed, wanted to say this:
I don't think it's cuz of any extension I use. I tried the same in Mozilla Firefox which I barely use and I have no extensions in it so it's pretty much like a newly added browser but anyway, I tried there and I have the same problem there too so I don't think this could be cuz of any extension and might be cuz of something else
Describe the issue
When typing in zen mode, it saves automatically, I guess it's supposed to save just once (per change) but it constantly tries to save the same thing again and again (even when you have made no changes after once) with a lot of POST requests which seems never ending in an infinite loop
I already tried
Steps to reproduce the behavior
Not sure if it's 100% reproducible but for me, it is, my project is a new one with about 700 strings and a few languages, if that helps
Expected behavior
Should just save it once
Screenshots
Exception traceback
No response
How do you run Weblate?
Docker container
Weblate versions
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: