I have tested this item ✅ successfully on 4bb2e3a

RTC

@laoneo can you have a look at this because i'm not quite confident with this.

Me neither, pretty sure this will introduce a regression.

@laoneo Could you please describe in more detail why this would introduce a regression?
The only problem I still see are disabled fields which are also required, but we already have the problem and I can take care of that in a next step.

@laoneo @HLeithner I have restored the previous state, as I do not really fully understand when a default value is needed. The only adjustment now concerns what, according to the description, anyway should not be.
If the field is disabled, and the browser still sends data, then I will delete it again.
I hope now there should be no reason to hold back the fix.

@degobbis can't say exactly what, it is just so a feeling. It took a couple of iterations till we were on a stable state with all these readonly, disabled states and access level settings including the passed array. What I can remember is that we had issues with values not being present in the data array as they were needed to clear values, etc.

@laoneo However, we are currently receiving an error message because the values from disabled fields are still sent. With my fix, I'm only making sure that the described procedure of the Bowser is actually executed. Either way, the same result.

@gogicomputers @viocassel Could You please test my changes again?

I have tested this item ✅ successfully on 174136c

Status "Ready To Commit".

Thanks for tests.

thx