This is caused by what we consider to be breaking changes in Chrome. Their argument is that it is expected as part of a forward-thinking approach, and other browsers will soon be following suit. We're aware and have an open ticket to fix it soon within Ignition. I'll try to get a Dev to chime in with the recommended short-term workaround.