I'm not sure if you are using WP-Juicebox (the Juicebox plugin for WordPress) or trying to embed your gallery manually.

If you are using WP-Juicebox and find that the pop-up window does not display the gallery settings when you click the 'Add Juicebox Gallery' button, then please see this forum thread for suggestions.

If you are trying to embed your gallery manually, then I would recommend using the baseUrl method documented here.
Essentially, once you have created your gallery with Lightroom, you would upload the complete gallery folder (not just the contents) to your web server and paste the baseUrl embedding code into the body of your WordPress page or post (ensuring that the method of entry is 'Text' rather than 'Visual'). It does not matter where on your web server you upload your gallery folder to as long as the two paths in the embedding code (the path to the 'juicebox.js' file and the baseUrl itself, pointing towards the gallery folder) are correct.

For example, if your gallery folder is named 'my_gallery_folder' and you upload it to the root directory of your web space, then you could use the following embedding code. The leading slashes in the paths denote your root directory so this code will work in any web page throughout your site without modification (although you can change the gallery dimensions and background color if you like).

<!--START JUICEBOX EMBED-->
<script src="/my_gallery_folder/jbcore/juicebox.js"></script>
<script>
    new juicebox({
        baseUrl: "/my_gallery_folder/",
        containerId: "juicebox-container",
        galleryWidth: "100%",
        galleryHeight: "600",
        backgroundColor: "#222222"
    });
</script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->

If you have trouble with WordPress adding <br> and <p> tags throughout the code, install the Raw HTML plugin and wrap the code in [raw] ... [/raw] tags.

I hope these notes help.
However, if you continue to experience difficulties, please post back with a link to your gallery's web page so that I can see the problem for myself and hopefully help further.

I have tested your setup in Chrome 54, Edge, Firefox 49.0.1, Internet Explorer 11 and Opera 40 on my PC.
Every time I single-slick your gallery's Back Button, the animation on your Edge Animate page is active without having to click anywhere on the page. It works in all browsers for me.

The Back Button is essentially just an <a> tag (like your manual link) which is generated dynamically by the 'juicebox.js' file when the gallery is displayed (although this should make no difference).

Maybe some additional information would help to track down the cause of the problem.
What version of Safari do you use?
Do you have any browser extensions installed? If so, try temporarily disabling them to see if this helps.
Try completely clearing your browser's cache before reloading your website to see if this makes a difference.
Also, try other browsers to see if the problem is unique to Safari.

Hyperlinks operate with a single-click and, as far as I'm aware, there is no way to simulate a double-click on the Back Button when a user single-clicks it.

Tapping the screen on an iPhone toggles the overlay on and off by default (you can override this behavior by setting showInfoButton="TRUE") but tapping a button on the Button Bar should certainly still work. If you have a gallery where this does not work, please post a link so that I can investigate further. (I have just viewed the gallery whose link you posted and the Button Bar buttons seem to function fine on my own iOS device.) Also, check to see if you have any custom CSS which might be overriding the gallery's own CSS.

Instead of using a <form> tag, try using a regular <a> tag instead. You can then style the content of the tag using CSS.
This should hopefully work. (The <a> tag link in the first image in this demo gallery works on my iPod Touch.)

No problem.
I'm pretty sure Ryan should be able to help you out with the use of hook_juicebox_gallery_alter() over in the Srupal forum.

Normally, to give each gallery a different audio track, you would just assign each gallery different audioUrlMp3 and audioUrlOgg values.
For reference, a list of all Audio Options can be found here.
Please also see the Adding Audio Support section.

The hook_juicebox_gallery_alter() method is unique to the Juicebox module for Drupal. It is not part of Juicebox itself.
The Juicebox module for Drupal is an unofficial plugin which was not written by ourselves and, as such, I am not familiar with hook_juicebox_gallery_alter().
I would recommend that you post your query in the Drupal forum where the author of the module should be able to help you further. (The module is well supported by its author over there.)

I realise that this may not directly answer your query but I hope it points you in the right direction.

Unfortunately, Google (who acquired Picasa) do not seem to allow access to new Google Photo Albums via the Picasa Web API although existing albums created prior to the acquisition can still be displayed via WP-Juicebox (as long as they have not been modified recently).

This is by design. When the 'Open Image' button is clicked for a Flickr gallery, the image's Flickr page is opened.
There is no way to change this behavior using any available configuration options. The code which handles this is buried deep within the 'juicebox.js' file which is obfuscated and cannot be modified.

All I can suggest at the moment is to perhaps suggest this alternative action for the 'Open Image' button in the Feature Requests forum thread.
This keeps all the ideas together and ensures that they are not overlooked by the developers.
I do not know the likelihood of any suggestions being implemented but this is certainly the best place for all ideas.
Thank you.

You're correct. Sorry. The link pointed towards the Showkase forum Feature Requests thread in error. Thank you for pointing this out.
I've fixed the link now so that it points correctly towards the Juicebox forum Feature Requests thread (http://juicebox.net/forum/viewtopic.php?id=5). I'm glad you found the right thread. Apologies for any inconvenience caused.

@borut.podlipnik

You can change the shape of the thumbnails with thumbWidth and thumbHeight (via the 'Thumb Width' and 'Thumb Height' sliders in the 'Thumbnail' control panel). They do not need to be square but they will all be the same size as each other.

The thumbnails exported by Lightroom are not cropped (as you have discovered). Lightroom uses the thumbWidth and thumbHeight values as maximum bounds when resizing the images and their aspect ratios are respected.
However, Juicebox will always dynamically scale the thumbnail images to fill the thumbnail dimensions (with cropping if the aspect ratios do not match) when the gallery is displayed.
Even though JuiceboxBuilder-Pro crops thumbnails to the exact thumbnail dimensions and Lightroom does not, if you view galleries (built with JuiceboxBuilder-Pro and Lightroom) with the same thumbWidth and thumbHeight values, the galleries (and thumbnails in particular) will look the same.
There is no way to change this.

The only thing you could do is create your own set of scaled-to-fit thumbnail images (in Lightroom, Photoshop or another imaging program) and replace the ones in the 'thumbs' folder.
Please bear in mind that it would still not be possible to have thumbnail images of different sizes. All thumbnail images will be displayed at the thumbWidth and thumbHeight dimensions. If you have images of varying aspect ratios, you may need to pad your thumbnail canvas with blank space (at the top and bottom or left and right) to fill the thumbnail dimensions.

If you like, you can post suggestions for future versions in the Feature Requests forum thread.
This keeps all the ideas together and ensures that they are not overlooked by the developers.
I do not know the likelihood of any suggestions being implemented but this is certainly the best place for all ideas.
Thank you.

It is not possible to have the shared image's thumbnail displayed in the pop-up Facebook share window due to limitations imposed by Facebook on what data can be passed via their share URL. Only one thumbnail image can be used per web page. However, the shared link will still point towards the correct image within your gallery, though.

The image used in the pop-up Facebook share window is set using an Open Graph og:image meta tag in the <head> section of your web page, such as the following:

<meta property="og:image" content="http://www.example.com/images/thumbnail.jpg" />

Please see here for more details on the Open Graph protocol.

You can think of the og:image as being representative of the gallery as a whole so you could use an image which best represents your gallery. (The og:image does not need to be an image from the gallery.)

If you create a gallery with JuiceboxBuilder-Pro, an og:image meta tag will be automatically generated and included in the gallery's 'index.html' file (pointing towards the first image in the gallery). If you are embedding your gallery in an existing web page alongside other content, then you will need to add an og:image meta tag manually.

Although the thumbnail image displayed in the pop-up Facebook share window will always be the same one (specified via the og:image meta tag), the link being shared will still point correctly towards the shared image in the gallery. You should notice that the URL being shared ends with something like #2 or #17 where the number represents the image in the gallery. When a user clicks on a shared link, the corresponding shared image will be opened in the gallery.

If you really wanted to override Juicebox-Pro's click handler for the Facebook share button, you could try something like the following which will allow you to run your own custom JavaScript code when the Facebook share button is clicked.

<script src="jbcore/juicebox.js"></script>
<script>
    var jb = new juicebox({
        containerId: "juicebox-container",
        shareFacebook: "TRUE"
    });
    jb.onInitComplete = function() {
        $('.jb-bb-btn-facebook').off('click');
        $('.jb-bb-btn-facebook').click(function() {
            // Custom JavaScript code to be run when Facebook share button is clicked goes here
        });
    };
</script>

This uses the Juicebox-Pro API (specifically the onInitComplete event) to ensure that the Facebook share button is present in the DOM (Document Object Model) before any actions are performed on it.

Please note that Juicebox-Pro was not designed with this functionality in mind (user overrides for Button Bar buttons) and whilst you are free to use such modifications, they are not officially supported (and you may run into unforeseen problems that might have to be tackled along the way).

You're welcome.

By default, Juicebox will scale down large images to fit within the gallery's image area as large as possible whilst respecting their aspect ratios and without cropping. However, small images will not be scaled up (as this may decrease their visual quality).

If you find you have space surrounding you images, then make sure that your images are large enough that they would need to be dynamically scaled down slightly by Juicbox when the gallery is displayed. This will ensure that they are displayed as large as possible without cropping or stretching within the given area.

If you still have space to the top and bottom or to the left and right of your images, then please see this FAQ:
My Juicebox gallery shows too much space above or below the main image, how do I fix this?

Juicebox-Pro users have the option to change the way that images are scaled within the gallery's image area via the imageScaleMode configuration option. Possible values are SCALE_DOWN, SCALE, FILL, STRETCH and NONE.
Short descriptions of each of these values can be found in the Main Image Options section of the Config Options page.

Please note that imageScaleMode is a Pro-only option which is not supported by Juicebox-Lite (the free version).

Thank you for providing the URL to your gallery's web page.
I think the problem might be that your URL includes an IP address and a port number.
Try using your domain name instead (for your shareURL and when you access your web pages in your browser).
Hopefully this will solve your problem.