This bug is fixed in version 1.3.19. You might need to restart your browser to get it to update. Thanks for finding and reporting that bug.
