Hi @Wolfgang,
Thank you for bringing this to our attention!
This should now be fixed with 1.3. Kindly let us know if this is the case on your end.
Thank you!