Thank you for reporting this, @Lijn-B!
With 1.3, this issue should now be fixed. Please let us know if this is the case on your end.
Thank you.