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.

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 have successfully implemented this tweak on several systems, and saw success without even restarting Mango.

Thanks for the quick response and solution!

]]>https://forum.infiniteautomation.com/post/11748https://forum.infiniteautomation.com/post/11748Thu, 02 Jun 2016 01:33:25 GMTOne 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.

]]>https://forum.infiniteautomation.com/post/18772https://forum.infiniteautomation.com/post/18772Invalid DateHey 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
]]>https://forum.infiniteautomation.com/post/21159https://forum.infiniteautomation.com/post/21159Invalid DateHi 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
]]>https://forum.infiniteautomation.com/post/21161https://forum.infiniteautomation.com/post/21161Invalid Date