Hey there!
Thanks for sharing this. This is a known issue.
I’ve attached your report to the internal bug ticket!