I am afraid you are facing the same issue what was mentioned in the earlier post you cited here. Unfortunately this still exists.
For the easier follow up of this issue I am giving here the internal ticket number that was created earlier to fix this case [AP-15515]. I have added a +1 to this from your side.
In our changelog you can follow up whether this fix is implemented in the future releases or not.