Reduce impact of ApiColorPicker emit bug

[manuelmeister]

Use default autoSaveDelay to fix #4212

[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.

[usu]

This doesn't fix the bug - it must makes it a bit harder to get the timing right in order to reproduce 😄

Recording.2023-12-26.191728.mp4

To me this smells like a wrong handling of dirty data.

• outside value should not override local data if local data is dirty
• outside value should not trigger an API call

[manuelmeister]

@usu I agree, sadly the colorpicker always emits when the input value doesn't match the exact VColorPicker color object (which is never). This would need a wrapper component to encapsulate the colorpicker.

[manuelmeister]

@usu I couldn't easily fix the picker problem. I did manage to prevent an api request if the value changes from the outside. I think we could fix the dirty problem in a separate PR.

[manuelmeister]

@usu I think my PR already provides a real improvement. Could you have a look again?

[BacLuc]

The experience is better than before.
For most users it will be enough

[usu]

@usu I couldn't easily fix the picker problem. I did manage to prevent an api request if the value changes from the outside. I think we could fix the dirty problem in a separate PR.

Opened a new issue for this at #4404