I do know Chrome is 100% compatible with the latest UI (I use Chrome as my primary browser for development in CloudStack), but it is also very aggressive with caching (even more so than IE in some cases!). After an upgrade/installation which contains UI updates, you may want to clear out all cached data for the management server domain. Unfortunately there isn't much of a workaround that I know of beyond this, but I've definitely experienced issues with the UI being corrupt even after multiple refreshes of the UI. Also, check your management server installation (i.e., tomcat folders) to make sure that your server isn't keeping old server-side files around.
-Brian -----Original Message----- From: Ron Wheeler [mailto:rwhee...@artifact-software.com] Sent: Tuesday, November 12, 2013 12:54 PM To: users@cloudstack.apache.org Subject: Re: UI problems in Chrome In light of the other reports of Chrome working, I would just do part of what I suggested - look for hints in the logs to see what specific problems are occurring. I would also check it on other workstations and from other network locations, if that is possible, to see if the problem is restricted to a particular machine or to part of your network. If you can try your Chrome browser against a public Cloudstack install that is known to support Chrome, that might give you some hints. Ron On 12/11/2013 3:17 PM, Ron Wheeler wrote: > You could tell them that Chrome doesn't support the CloudStack UI. > That might put it in a better light! > > You should at least file a JIRA with some specific examples and any > errors reported in the Chrome console or system logs. At least it will > tell people that it needs to be fixed and give them some hints about > where to look for the problems. > > Ron > > On 12/11/2013 3:09 PM, David Matteson wrote: >> Hello, >> >> Looking in JIRA I didn't see one ticket describing all the problems >> we have with the Cloudstack UI in Chrome; the login form only works >> intermittently, most of the views (Instances, Service Offerings, >> etc.) don't work properly, and in general it just seems broken. >> >> In Firefox, however, it works flawlessly. This is on Mac OS X, both >> Mountain Lion and Mavericks. >> >> Anyone else experience this issue? Is it known. I noticed that Chrome >> is not listed among the browsers in the UI documentation? I don't >> know if that's significant, though. >> >> This is problematic as we'd like to make the interface available to >> some customers, but telling them "It's broken in Chrome." sure isn't >> good. :) >> >> Thanks. >> > > -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102
