Bugfix: Prevent wrong dirty reset

[manuelmeister]

Initially, we reset the dirty flag before each save request.
My PR defines dirty as "local value is not the same as api value", on devel it is currently defined as "time between entering a different value and starting to patch to api".

Some api fields have a InputFilter/Trim in the backend, which means that the api value returned will never contain spaces around the value. If the user leaves the input, the localValue should be reset to the apiValue, to correctly represent the actual db value, without disrupting the user.

Closes #3875

[github-actions]

⛔ Feature branch deployment currently inactive.

If the PR is still open, you can add the deploy! label to this PR to trigger a feature branch deployment.

[carlobeltrame]

Perfect fix, thank you!
I think this also fixes #4404, is that possible? I wasn't able to reproduce it anymore, even with extremely throttled network connection

[manuelmeister]

@carlobeltrame I don't know, that would be totally awesome of course 😂

[manuelmeister]

@usu can you also check this, to make sure I did not make any mistakes or errors of thinking.

[usu]

@usu can you also check this, to make sure I did not make any mistakes or errors of thinking.

Sorry, didn't manage to test this before it got merged. It seems that on blur, the dirty flag is not properly reset (see screen recording below).

Screen.Recording.2024-03-24.at.11.03.44.mov

My PR defines dirty as "local value is not the same as api value", on devel it is currently defined as "time between entering a different value and starting to patch to api".

The 2nd seems like a bug to me, but the first one is also problematic. I labeled #2578 with "Meeting discuss" we we can have a look at it during next meeting.