With the release of Safari 6.1 (for OS X 10.7 and 10.8) and Safari 7 (OS X 10.9) Apple has taken a sandboxing approach to Oracle's Java plugin whether or not the applet is signed. This has a critical impact on EditLive! and its ability to perform some typical tasks.
There are four primary functions that will no-longer work with the new default Safari configuration:
Browsing for local files to insert
Accessing Microsoft Word HTML clipboard content
Access to a persistent storage area
Executing a tool to read RTF clipboard content
On the first load of a page containing EditLive!, the following prompt appears. Clicking "trust" now only allows the plugin to run, it does not remove Apple's sandbox restrictions.
After trusting Java, attempting to insert a local image now shows an invalid browse dialog:
You can configure Safari to allow Java to run with no security restrictions, but this involves changing a setting in Safari's preferences. This will enable all EditLive! to function correctly. Please note that this is a per-workstation change. To properly configure Safari please perform the following steps:
1. In the Safari menu, click Preferences.
2. Click the Security tab, then click Manage Website Settings...
3. Click the Java plugin on the left, then click the dropdown next to your site that includes EditLive! (this example uses ephox.com.)
4. Select Run in Unsafe mode.
5. Select Trust on the security warning that appears.
Note: This has to be done for each website where the end user accesses EditLive!.
6. Click the Done button to apply the new settings.