i've seen issues like this happen between browsers - the issue stemmed from URL mismatches within ServiceDesk/ProcessManager. for example - the certificate for HTTPS was configured to use https://helpdesk, however, the root URL for some processes was being rendered as https://servername.domain.com/website. in IE on a Windows workstation tickets were not workable, as some textboxes and other page controls did not work. in Chrome, the controls worked. in Safari, the controls worked oddly, like neither chrome nor IE. in IE on the local Workflow server, the controls worked, whereas Chrome did not.
this is all to say that URL mismatches wreaked havoc with the page controls, but did so differently depending on which browser and OS was being used to access the ServiceDesk.
perhaps try reviewing the links below (the topics/subjects may not seem to pertain directly to your reported issue, but the validation checks should afford the same result) and ensure that all your URLs are configured properly. the articles linked below should help you find all the URL configuration locations (be sure to review the entire article and any responses)
http://www.symantec.com/business/support/index?page=content&id=HOWTO98406
https://www-secure.symantec.com/connect/articles/enable-ssl-servicedesk-71-after-post-install-wizard-finishes
of course it may not have anything to do with the URLs, but it'll do to check.
-andrew