Yeah this is known issue with Chrome as of now. I think devs already mentioned that there is nothing they can do about it so you have to either get used to it or use different browser