That is a known bug is v5.3.8
It’s fixed in v5.3.10 which should be hitting the Chrome WebStore anytime now