I already reported this, see
tl;dr: it's an issue with chrome on MacOS that Snap! can't actually control.