I have checked this on the latest Chrome version and looks like it's fixed by itself. Should we apply hotfix in this case? Do you expect that this thing could be broken in the future?

Hi aemmarc. Do you guys expect that this issue will be resolved with the future Chrome updates or do we need to wait for some fix from you? As our project supports only Chrome and we do not want to switch users between browsers for stuff like that. Thanks!