Hello, this bug is still present in 5.14.2 - I've just hit it. Are there any plans to fix it? Best regards, Stephan