Known Issues and Unsupported Features

Using vSphere Client script plug-ins with the vSphere Web Client has the following known issues.

■

Setting the display attribute on a URL tag to a value of "none" runs the script located at the URL without opening the URL in a new page. This behavior is supported in the vSphere Web Client, but the Flash Player requires the domain where the script is located to have a cross-domain policy XML file. See http://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html.

■	When using a script plug-in at a secure URL (HTTPS) in the Chrome or Firefox browsers, you must load the script plug-in page in an external tab at least once before it appears in the vSphere Web Client.

■	Icons for a script plug-in shortcut do not appear in the vSphere Web Client. The vSphere Web Client displays a placeholder icon for the script plug-in icon on the home screen.

■	Localized labels for script plug-ins are not supported in the vSphere Web Client. The vSphere Web Client displays all titles and labels using the English (EN) locale.

■	Toolbar extensions are not supported in the vSphere Web Client.

■	Script plug-ins that provide shortcuts to specific vSphere objects or object views are not supported in the vSphere Web Client, as the datacenter hierarchy is organized and displayed differently than in the vSphere Client.