This issue still persists on version 4.3.1. Is there a reason it's not resolved for more than a year. It's very serious one and there is no reasonable workaround.