Administration Guide : Configuring the Xinet server for Drag and Drop and Linked files : InDesign Drag and Drop on Macintosh: Troubleshooting

InDesign Drag and Drop on Macintosh: Troubleshooting
Xinet Support ID supports dragging and dropping from browsers running on Macintosh client machines directly in to existing image boxes or the background spread for Adobe InDesign CS6 through Creative Cloud (CC) 2017.
When users run the client installer on client machines, the necessary plug-ins should be installed to enable this support for Safari. These include plug-ins for Adobe InDesign and Safari. Google Chrome is also supported using an Extension available by searching for "Xinet" on the Chrome Web Store.
If you are having trouble downloading files through drag and drop to a browser:
Note: This material applies to downloads through browsers. These issues should not be present for Pilot.
Safari Configuration: Allow JavaScript from Apple Events
For Safari, the download is started by sending Safari some JavaScript via an Apple Event. Safari 9.1.2 has a Develop menu preference "Allow JavaScript from Apple Events," which must be checked. To see the current value and check if it's necessary, you may need to check "Show Develop menu in menu bar" in Safari's Advanced Preferences:
Once enabled, the "Develop" menu includes an "Allow JavaScript from Apple Events" menu item which must be checked. (The default value for this option was changed to false in OS X 10.11.5 El Capitan and macOS 10.12 Sierra, so you now have to check it yourself.)
Final File Destinations
If you are using a remote workflow, the file is downloaded as a zip file. The plug-ins will then decompress it if necessary (using the Archive Utility app), and move the file to its final destination. The location depends on whether the InDesign document has been saved or not:
Note: There are two drag and drop workflows that are supported: local and remote. These workflows determine how the plug-ins handle files and look for files.
For this process to work correctly, the Xinet Support ID plug-in must be able to find the file that is being downloaded. It could be accessing files in any of the following three places (and needs permission to access these places):
Local Workflow
If the volume that is being displayed in the browser is mounted on the user's Desktop, then dragging and dropping on to the InDesign document will link to the file from that mounted volume. If both the high-resolution and For Position Only (FPO) volumes are mounted, then the plug-in will link to the image from the high-resolution volume by default (to encourage the use of high-resolution images). However, if only the FPO volume is mounted then its images will be linked.
Once the URL has been determined from the drag, the browser is not used further-making this local workflow easier to support than the remote workflow described below.
Note: Google Chrome does not use the standard drag and drop "flavor" for URLs, so the plug-in needs to do additional processing to find it (and may take additional time). This code has only been tested on Chrome version 52.0.
Remote Workflow
If the volume is not mounted, then the Xinet Support InDesign plug-in will instruct the browser to download an EPS FPO file of the image that is dragged onto the InDesign document. This download could be to one of several locations, as described above.
Firefox 45 Additional Configuration
Important! Firefox 45 ESR is the last version of Firefox that is supported by Xinet, and will no longer be available from Mozilla after June 13th, 2017. Safari and Chrome will be the only supported browsers going forward and we strongly advise that you move to one of these browsers now. If you want to continue to use Firefox for the time being, you will need to do the additional steps outlined below.
To prepare for the deprecation of Firefox support, we have moved the Firefox plug-ins from the default Xinet Contextual Menu (CM) installation, and placed them in a separate "Firefox ESR 45.0 Support" package in the Client Installer (disabled by default).
In addition, the following workaround is required to enable Support Contextual Menu Plugins and Add-ons for Firefox 45 ESR: