This issue should be solved in 4.3, but it’s still present in 4.4.1beta1
Thanks for pointing this out again @josklever .
The issue will be fixed for the 4.4.1. release.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.