Yes. You can use the swipe gesture to change images in a Juicebox gallery when viewed on an iPhone and on other mobile devices which support the swipe gesture.
Try viewing our demo galleries on your iPhone.

This is a known issue which affects only Firefox and, as you have discovered, only happens when previewing galleries locally on your computer (and not when the galleries have been uploaded to a web server).
I think this issue is likely to be related to the issue you reported in this forum thread. It certainly seems to manifest itself under similar conditions (same browser, local only and hovering mouse over problem area clears it).
A bug report has been logged but a solution has not yet been found.

Open the 'changelog.txt' file in the skin's folder ('Tools -> Open Directories -> Skin directory') to check which version of the skin you have installed.
The current version of the skin is v1.2.0 and it can be downloaded from here.
I will include the skin's version number in the skin settings interface in the next version.

The drop shadow for the captions is not configurable from within the JuiceboxBuilder-Pro interface.
Edit the 'jbcore/classic/theme.css' file in a plain text editor and remove line 215:

text-shadow: 1px 1px 2px rgba(0,0,0,0.5);

(The line number refers to Juicebox-Pro v1.2.0.)

Your gallery scales OK in Firefox on my PC (in that the size of the main image and the number of thumbnails displayed changes dynamically as the size of the browser window changes). Please note that although the number of thumbnails displayed changes, the actual size of the thumbnails does not.
Your web page has scroll bars because the total width and height of all elements on your page add up to greater than the width and height of the browser widow.
For example, your gallery has been given a height of 100% but your page also has a navigation menu header was has a finite height to add to this.
If you wish to have a resizeable gallery with a header and no scroll bars, please see the Using a Resizable Gallery with a Header section of the Juicebox - Embedding Guide, specifically the View Resizable Gallery with Top Menu Example. You can view the source of the page in your browser and modify it to suit your needs.

As I mentioned above, I have already notified the developers of this but I would also encourage you to post feature requests in this forum thread. It keeps them all together and ensures that they are not overlooked. Thank you.

You could point each Juicebox gallery created by svManager towards the master 'jbcore' folder by editing the 'svmanager/plugins/juicebox/jbmaster/index.php' file in a plain text editor and changing line 27 from:

<script src="jbcore/juicebox.js"></script>

... to:

<script src="http://www.example.com/svmanager/plugins/juicebox/jbmaster/jbcore/juicebox.js"></script>

... changing 'www.example.com' in the example above to your own domain name.
The 'jbcore' folders in each gallery folder would then become redundant (though deleting them may have unwanted knock-on effects within the svManager admin area which expects the folders to be there).
Please note that the line number refers to svManager v1.8.3.

If creating your Juicebox galleries with Lightroom and importing them into svManager, you would need to manually alter the path to the 'juicebox.js' file (in each gallery's 'index.html' file) to point to the master 'jbcore' folder within your svManager installation. However, by doing so, you would be unable to view the gallery locally and it would function only when uploaded to your web server.

Yes. Many bugs were fixed in v1.2.0.
Please see the Juicebox - Version History for a full list of changes.

No. Just make sure that all galleries are of the same version. Otherwise, if multiple different 'juicebox.js' files are loaded on the same page, one will take precedence over the other(s) and you may experience unexpected results.
If the WP-Juicebox plugin is enabled, then the 'juicebox.js' file from within the plugin will already be loaded on the page and you will not need to include the call to 'juicebox.js' within your manually embedded Juicebox gallery.

That is correct. svManager (unlike WP-SimpleViewer) creates an individual folder for each gallery and copies the master 'jbcore' folder into each gallery folder.

This is not possible through any of svManager's preconfigured options. It would require modification of the svManager source files.

I am glad that your problem has been resolved.
Thank you for posting back to let me know.

First of all, please see this Juicebox support section on Screen Modes.
Setting showLargeThumbs="FALSE" will initially hide the thumbnails in Large Screen Mode.
If you wish to prevent the viewer of your gallery from ever being able to show the thumbnails, you should also set showThumbsButton="FALSE".
Setting showSmallThumbs="FALSE" will disable both the thumbnail page and the thumbnail button in Small Screen Mode.

All galleries created by WP-Juicebox share the same 'jbcore' folder.
This allows the user to upgrade all galleries in a single action, when a new version of Juicebox is released, by replacing the 'jbcore' folder in the 'wp-plugins/wp-juicebox/' folder.
When WP-Juicebox is enabled, the 'wp-plugins/wp-juicebox/jbcore/juicebox.js' file is automatically loaded on the page.
Therefore, if embedding galleries manually into WordPress (instead of using WP-Juicebox), then you should deactivate WP-Juicebox.

When embedding your gallery manually, your WordPress theme is inserting <p>, </p> and <br /> tags throughout your embedding code.
If you are not already doing so, try inserting your embedding code into your post with the method of entry set to 'HTML' rather than 'Visual'.

Sure. I can confirm that your suggestion of adding:

# Juicebox skip/bypass rule
RewriteCond %{REQUEST_URI} ^/wp-content/plugins/wp-juicebox/ [NC]
RewriteRule . - [S=13]

... to the root .htaccess file works fine, although I had to change it to the following in my own WordPress installation:

# Juicebox skip/bypass rule
RewriteCond %{REQUEST_URI} ^/wordpress/wp-content/plugins/wp-juicebox/ [NC]
RewriteRule . - [S=13]

...  so Skippy should use: