GrimLink opened this issue 2 years ago · 1 comments
This seems a Chrome bug, that causes this behavior, closing this since there is nothing we can do for now except report this issue at Chrome.