I have reported it through a Help Center Request . I urge more folks to do this. The more reports, the more focus the issue gets. IIRC, there were a number of things broken in the Chrome update near the beginning of last month (about the time of the earliest post in this thread, and reinforced by the fact that it is not an issue in FireFox). Hopefully this is something the dev team can solve without too much more time. In the meantime, as annoying as it is, there are at least some workarounds.