We cannot seem to reproduce this — I’ve gone ahead and opened an issue for the developers to review:
Can you all confirm that the issue is present after updating to the latest version of the browser (1.59.117 at the time of writing this)?