Hi @Wolfgang,
Thank you for taking the time to report this!
With 1.3, this should now be fixed. Kindly let us know if this is the case on your end.
Thank you.