Thanks for the video! The team was able to reproduce this issue and is working on a fix. Here's the bug reporter link!