Should it stay possible to store empty mandatory fields at updating data in draft mode?

In v3.2.3 it is possible to save empty mandatory fields, when you update a collection entry in draft mode.
At creating the entry this is not possible and I think it would be better, if this is also impossible in updating an entry.
It would help to be sure, that the mandatory fields are present for manipulation in lifecycle hooks.
So I am not sure if this is a bug or a wanted behavior. What do you mean?

@alexandrebodin @Convly @Pierre_Noel is this intended? If not then @pointout I may need you to open up a bug report (it can wait until the backend engineers confirm this).