I'm glad it works. Thank you for letting me know.

Yes. If you want to use larger images (assuming you have larger images uploaded to your Picasa Web Album), then you can increase the imgmax value to use them.

There are still <p> and <br /> tags throughout your gallery's embedding code and this is the cause of the problem.
They are more than likely to have been added by WordPress's wpautop function and you'll need to remove them to remove the space above your gallery.

I'm not sure what you mean by "added the wpautop function". You need to disable the function rather than add it.
Even if you have disabled it, the tags may still be present in the body of the post (having been inserted prior to disabling the function) and you might need to remove them manually. Check the embedding code in the body of your post to see if they are still there and delete them if they are.

If you have used one of the wpautop plugins, perhaps you could try another. There are several that you could try.

If you continue to experience difficulties, then I would be happy to help further but it would help if I had access to your web server and WordPress installation. If you are agreeable to this, then please let me know and I will send you an email address where you can forward your login details to me.

It looks like there might be an issue (an escaped '&' character) with the query string for the Picasa feed.
Please open the 'wp-juicebox/wp-juicebox.php' file in a plain text editor and replace line 1366 with the following:

$picasa_feed = 'http://picasaweb.google.com/data/feed/api/user/' . $this->remove_whitespace($picasa_user_id) . '/' . $term . '/' . $name . '?kind=photo&imgmax=1600';

This should hopefully solve the problem.
Please let me know how you get on. If the suggestion above works fine, then I will ensure that the bugfix is included in the next version of the plugin.
Please note that the line number above refers to the current version of WP-Juicebox (v1.4.4.1).

Make sure that you set enableAutoPlay="TRUE" (in JuiceboxBuilder-Pro's 'Customize -> AutoPlay' section) to enable the AutoPlay keyboard controls (the default value for this configuration option is FALSE).
Also, if your gallery is embedded in a page alongside other content (rather than being a 100% x 100% gallery taking up the full page), then be sure to click somewhere in the gallery first to give it focus.
If you want to automatically give your gallery focus after the web page has loaded, then you could try something like the following:

<script type="text/javascript" src="jbcore/juicebox.js"></script>
<script type="text/javascript">
    var jb = new juicebox({
        containerId: "juicebox-container",
        galleryWidth: "600",
        galleryHeight: "400",
        enableAutoPlay: "TRUE"
    });
    jb.onInitComplete = function() {
        $('#juicebox-container').find(':first-child').focus();
    };
</script>
<div id="juicebox-container"></div>

If this still does not work, then please post the URL to your gallery so that I can take a look at the problem for myself and hopefully help further. Thank you.

I would encourage you to post your suggestion in the Feature Requests forum thread.
This keeps all the ideas together and ensures that they are not overlooked.
I do not know what suggestions will be implemented in future releases but this is certainly the best place for all ideas.
Thank you.

Thank you for providing the test galleries and for confirming that the problem happens only on iOS 8 (and not iOS 7).
I have been able to replicate the problem in a test gallery of my own (which I have provided for the developers) so there is no need to keep your test galleries active if you don't want to (but I very much appreciate you going to the trouble of creating them and doing more testing).

No. This should not cause any issues at all.

You can ensure that your web site serves a compressed version of the 'juicebox.js' file (and other files, too, if you like) by employing one of the techniques described on this web page. This will compress the files on-the-fly as required before serving them to the browser.
GZIP compression will not cause any problems and a Juicebox gallery will still work fine with the following sample .hatccess code in place as long as the browser being used to view the gallery can handle GZIP compression (most modern browsers).

<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/xml
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/rss+xml
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/x-javascript
</IfModule>

Please let me know what versions of Lightroom and the Juicebox-Pro plugin you are using.
If you are not already using the Juicebox-Pro v1.4.4.1 plugin then you might like to try upgrading it.
You can find the latest version inside the Juicebox-Pro download zip package.
Full instructions for downloading the latest version of Juicebox-Pro can be found here.

I have just tried watermarking images (with text and an image) in the 'Output Settings' control panel of the Juicebox-Pro v1.4.4.1 plugin in Lightroom v5.7.1 and Lightroom v6 and the gallery and images export fine with no problems.

Does the problem happen only with the Juicebox-Pro plugin or with other Web Engine Layout Styles too?

Maybe the problem lies with your source images. Perhaps you could upload one somewhere (a file sharing site such as Dropbox) so that I can try to replicate the problem with one of your own images. Thank you.

Please post the URLs to any of your galleries that fail to display in Firefox 40.0.3 and I'll take a look at them and let you know what I find.

It should not be necessary to use absolute paths in your embedding code.
The leading slash notation (to denote your root directory) should work just fine but you could also try using standard relative paths (relative to the web page containing the gallery's embedding code).

Make sure that you clear your browser's cache after making any changes and before reloading your gallery's web page.

I'm glad you've been able to resolve your problem.
Thank you for posting back to let me know.

You should be able to just load the 'juicebox.js' file with a <script> tag at the top of your gallery's embedding code but if you were to have multiple galleries displayed on a single dynamically-generated page, then you might end up with multiple instances of the 'juicebox.js' file being loaded. (It should be loaded only once per page rather than once per gallery.)

In a WordPress environment, it is certainly a good idea to enqueue the file to load in your web page's <head> section.
This ensures that the 'juicebox.js' is always loaded and is loaded only once per page.

Also, the 'juicebox.js' file must be loaded from within the 'jbcore' folder. If the code is minimized by a third-party plugin and loaded from a different location, then this will break the gallery.

This sounds like it might be a problem with Lightroom rather than with the Juicebox plugin.
The resizing and exporting of images is handled by Lightroom itself.

Does this happen when you try to create a gallery with the same images using a different Web Engine (something other than Juicebox) but exporting at the same image size?

What version of Lightroom are you using and how much RAM does your computer have?
Try creating a test gallery with fewer images to see if this makes a difference.

Also, check that you are not exporting your gallery to a restricted (read-only) folder or to a network drive.
Try exporting to a folder on your desktop to see if this helps.

I understand that the web site noted in your original post is not your own and that the owner of that site's requirements (such as the use of a folder named 'webbtest') may be confusing matters.
I realise that you were quoting from another thread but I thought it might have been one of your own (with details that referred to your own web site).
Sorry for any confusion my earlier replies might have caused.

If you are having trouble with some images displaying in a gallery, then the most likely causes are either:
(1) Images are not uploaded to the web server (or perhaps in the wrong location).
(2) Image file names do not exactly match the imageURL entries in the gallery's XML file, as noted in this FAQ.
(3) Permissions on the image files (or the 'images' folder) are too restrictive and the browser is unable to read them. Default permissions of 755 for folders and 644 for files should be fine.

If you could please post or email me the URL to your gallery's web page so that I can see the problem for myself, I should hopefully be able to help further. Also, as I noted in my email to you, I would be happy to log into your web hosting account and take a look at things for you if you like. If you'd like me to do this, just email me your login details and let me know where your gallery files are on your server. Thank you.