Concurrent ajax submits cause user data loss

@bogdan.dinu you said this has been resolved? Do you know where it was fixed? So we can track down the ticket and move over credit for users who helped here.

@smustgrave unfortunately no. I don't know where this was fixed. I just tried locally on D9.4 without the patch and saw that there is no more data loss.

This issue is pretty old, so it might have been #2837022: Concurrently editing two translations of a node may result in data loss for non-translatable fields → or a similar issue.

We could also mark it duplicate of 📌 Offer concurrent editing protection for all entities by including the changed timestamp to each entity form Needs work maybe which is still active and covering similar ground.

Will move over to 📌 Offer concurrent editing protection for all entities by including the changed timestamp to each entity form Needs work

This is not fixed, I'm still experiencing this on a Drupal 9.4.9 project with bricks form and on a Drupal 9.5.9 project with paragraphs.
And how could this be marked as a duplicate of an issue tied to the entity system component? That's disregarding the comment in #41 about non-entity forms that made catch move this to the forms system component.
I also disagree about the category change. To me, if a form breaks when clicking on a button, it's a bug (sorry if there's something I'm not aware of about issues categorizing).

Hiding patch per #49.

Ok, I think I see.
The issue's title and summary focus on the backend part of the problem, which should indeed be handled by validation.
But what brought me here is the mess caused by this bug on frontend: when it occurs, the whole paragraph/brick subform gets replaced by other unrelated fields.
What can be lost is not saved data, just contributed content.
Unless I miss something, I don't think this will get fixed with 📌 Offer concurrent editing protection for all entities by including the changed timestamp to each entity form Needs work , will it?
If not, what's the best way to handle this, change this issue's title and summary or create a new one?

Rerolled patch #33.

Here's patch #33 re-rolled without mysterious filename change...

Can the issue summary be updated to include why this is different then the related issue. + remaining tasks, etc.

Also please include any interdiff

Fixed build error and attached interdiff for same. and updated issue summary

Patch needs to be updated for 10.1.x-dev,

Maybe even 11.x-dev at this point.

Re-rolled patch #61 for 10.1.x-dev.
Needs review.

Tried to fix failed custom commands.

We really should target the latest development branch and backport

I have re-rolled the patch #61, for 11.x-dev. please review

Can the issue summary be updated with proposed solution.

"We need to solve this both in FormBuilder" but how is it being solved? Helps the reviewers.

Rerolled patch #64 for 10.2.x, as it doesn't apply there

Uploaded the wrong copy -_-

Rerolled patch #64 for 10.2.x, as it doesn't apply there