Hello,
I’m pending on this issue to be resolved for the latest alpha versions.
As you can see in the issue tracker, it’s been marked as solved for 2019.3.0a7, however it’s still a known issue for 2019.3.0a7.
Should a new bug report be created for this?
Hey turdann,
This issue should now be fixed in 2019.3 (I’ve just tried in the latest 2019.3.0a11) and back ported to 19.2,19.1 and 18.4.
If it’s not fixed please let me know.
Thanks! Will test it as soon as possible 
Edit: Well, or as soon as .a11 is released.