Hi!

Unfortunately, after browser restart, I'm unable to reproduce this bug anymore :/ Same goes for v2 beta. But it's not the first time it happened to me, so I will keep you informed if it happens again. I'll try to investigate it deeper. I guess you can freeze this ticket for now.

Thanks for your response :)