Chrome not loading Data Sources page properly

[AldoRamos]

Upgraded to Chrome 51 and now my data sources page doesn't load.

Here are the error messages from the console:

VM1195:1 Uncaught ReferenceError: normal is not defined(anonymous function) @ VM1195:1g @ css.js.uncompressed.js:1a.onload @ load-css.js.uncompressed.js:185
dojo.js:1879 Error: timeout(…)(anonymous function) @ dojo.js:1879(anonymous function) @ dojo.js:362forEach @ dojo.js:93req.signal @ dojo.js:361(anonymous function) @ dojo.js:1641

Error: timeout(…)(anonymous function) @ dojo.js:1879(anonymous function) @ dojo.js:362forEach @ dojo.js:93req.signal @ dojo.js:361(anonymous function) @ dojo.js:1641
dojo.js:1882 src: dojoLoader
dojo.js:1882 info: Object {xstyle/css!dgrid/css/dgrid.css: 1, xstyle/css!dgrid/css/extensions/ColumnResizer.css: 1}

Do either of those error messages mean anything to you?

[AldoRamos]

FWIW: purged, rebooted, opened in a single tab; no change :(

[Woody Beverley]

Hey Aldo,

Thanks for bringing this to our attention. I upgraded Chrome on my MacBook Pro and was able to reproduce this problem. We are investigating. As soon as I have more information I will (or someone from IAS) will post here.

[phildunlap]

Hi Aldo,

Thanks for giving us the information needed to swiftly examine this issue. I googled, and it looks like Chrome 51 made some changes that caused problem in Dojo, and more specifically the xstyle library.

I was able to remedy the problem by installing the latest xstyle files into Mango/web/resources/xstyle/ then clearing the browser cache and deleting the Mango/work/jsp directory.

I downloaded version 0.3.2 of xstyle from here: https://github.com/kriszyp/xstyle/releases/tag/v0.3.2

We will definitely review this and consider making this version the version packaged with Mango. I have made a git issue for this:
https://github.com/infiniteautomation/ma-core-public/issues/747

[AldoRamos]

Good news.

I have successfully implemented this tweak on several systems, and saw success without even restarting Mango.

Thanks for the quick response and solution!

[AldoRamos]

One important reminder: browsers may still have the old modules cached, so you need to empty their caches before they can correctly render. Most significantly, you'll see the old behavior if you go to another computer (or browser) that still has it cached, even though you've seen it work on your initial browser.

A coworker discovered this, as he went to view the screen and it still failed on his screen. Cache flushed, problem solved.

[AldoRamos]

Heads up: this issue appears to have resurfaced; the same solution still works, but download the latest version: https://github.com/kriszyp/xstyle

[phildunlap]

Hi Aldo,

Yeah, we'd caught this and fixed it in the latest, you shouldn't have had to do that if you're on 3.4.4 release: https://github.com/infiniteautomation/ma-core-public/commit/209db3ddad42b9735bba43a98db25ca9c8eb6747

[psysak]

Hey guys, just FYI this still seems to happen from time to time even clearing cache and everything else doesn't solve the issue. Firefox is the answer

[phildunlap]

Hi psysak, is that instance up to date? If not, Jared's explanation of the permanent fix toward the end of this thread may be of interest: https://forum.infiniteautomation.com/topic/3551/data-sources-does-not-appear/14