This issue has been fixed in the next stable version of Chrome (version 61). They were unable to merge the fix in the current version (60) due to breaking changes. It was released only in the official beta version and this fixes the problem.
Here's what you can do to fix the problem for now:
- Install the beta for your client.
- Use one of the JavaScript workarounds described in the comments.
- Show end users how to deal with this problem by simply adding a new Chrome tab to the browser and return to the problem tab.
source
share