This is possible in Juicebox-Pro but not in Juicebox-Lite (the free version) by setting imageClickMode="OPEN_URL" and assigning URLs to the images via the linkURL entries on JuiceboxBuilder-Pro's 'Images' tab.

I'm not quite sure what you mean but it sounds like you might want to use a Splash Page.
The Splash Page is a placeholder for the gallery which, when clicked, will open the gallery fullscreen.
Please see this sample gallery for a demonstration.
For more information about the Splash Page, please see here.
The Splash Page can be configured using these (Pro-only) configuration options. With Juicebox-Pro, you can force the Splash Page to always be displayed by setting showSplashPage="ALWAYS".

However, if all you want to do is choose the first image in your gallery, you can order the images in exactly the order you want on the 'Images' tab of JuiceboxBuilder-Lite (by dragging and dropping each thumbnail into a new position).

Our demo galleries function very similarly in Safari 5.1.7 as they do in other browsers on my own PC.

If you are referring to the smoothness of the slide transition, then this may vary slightly from browser to browser and may also be somewhat dependent on the computer hardware being used. The fact that you are also loading the gallery in a virtual machine may also be a contributing factor.

One possible thing that can be done to maximize the smoothness of the transition is to ensure that imagePreloading="NEXT" (Juicebox-Pro only) or imagePreloading="PAGE" (default setting used by Juicebox-Lite) so that the next image in the gallery is already preloaded by the browser and ready to be displayed when selected by the user.
(Most of our demo galleries already use such settings but I thought I should point it out for anyone creating their own galleries and currently setting imagePreloading="NONE".)

Please also bear in mind that Safari is no longer being developed by Apple for PC and Safari v5.1.7 is now over two years old.
As you have noticed, modern browsers seem to provide a smoother image transition and I would recommend using a browser which is actively being developed (Chrome, Firefox, Opera, Internet Explorer).

Enter your Flickr details (the same ones you use for your gallery) into the Flickr API Explorer.
The photo ids will be returned (along with other data) in the results box at the bottom of the page.

The problem seems to be originating from the following CSS in your '51924fc4b1f57.css' file (specifically line 6 - height: auto !important;):

img, video, .wp-caption {
    -moz-box-sizing: border-box;
    -webkit-box-sizing: border-box;
    box-sizing: border-box;
    max-width: 100%;
    height: auto !important;
}

These CSS rules are applied to all images on your web page, including those in your Juicebox gallery. Juicebox has no option but to inherit such generalized CSS rules.

Try removing this code (or applying the CSS rules to only those elements on your web page which require them through use of CSS selectors) and your Juicebox gallery's imageScaleMode should work as expected.

Elements within a gallery cannot be selected. This is by design to prevent areas of the gallery being highlighted with a blue overlay by the browser when a user clicks throughout the gallery.

One possible solution to the problem might be to display the current image's title and/or caption in a container outside the gallery using the Juicebox-Pro API (specifically the onImageChange() event and the getImageInfo() method). Here is an example. Just create a sample gallery with JuiceboxBuilder-Pro and use the code below as the gallery's HTML index page.

<!DOCTYPE html>
<html lang="en">
<head>
    <title>Juicebox-Pro Gallery</title>
    <meta charset="utf-8" />
    <meta name="viewport" id="jb-viewport" content="minimal-ui" />
    <style type="text/css">
    body {
        margin: 0px;
    }
    </style>
</head>
<body>
    <!--START JUICEBOX EMBED-->
    <script src="jbcore/juicebox.js"></script>
    <script>
    var jb = new juicebox({
        containerId: 'juicebox-container',
        galleryWidth: '600',
        galleryHeight: '400'
    });
    jb.onImageChange = function(e) {
        var index = e.id;
        var info = jb.getImageInfo(index);
        var title = info.title;
        var caption = info.caption;
        document.getElementById('text').innerHTML = title + '<br />' + caption;
    };
    </script>
    <div id="juicebox-container"></div>
    <div id="text"></div>
    <!--END JUICEBOX EMBED-->
</body>
</html>

The current image's title and caption are displayed in a container below the gallery (as well as within the gallery itself) and can be selected from this container.

Unfortunately, this is not always the case. Not all features of Flickr are available via their API.
However, although there is no indication on the page I linked to in my post above that their API supports the Large 1600 and Large 2048 sizes, I have entered a Photo Id into the flickr.photos.getSizes Flickr API Explorer and it returns the two new sizes with size identifiers '_h' (for Large 1600) and '_k' (for Large 2048) so it looks like it might be possible to request these sizes via their API. (The current size identifiers of Medium, Large and Original are '_m', '_l' and '_o' respectively.)

Perhaps you could suggest this for a future version of Juicebox in the Feature Requests forum thread.
I do not know for sure if it is possible and whether or not the developers will incorporate it into a future version but posting there keeps all the feature requests together and ensures that they are not overlooked.

Thank you.

I am glad that all is working again for you.
I will ensure that all fixes are incorporated into the next version of WP-Juicebox.
Thank you very much for reporting back.

Yes. The Expand Button is automatically disabled when a Juicebox gallery is loaded into a frame or an iframe.
This is noted in '2) Using an iframe' in the 'Using an External Gallery Folder' support section here.
The only way around this would be to embed the gallery directly into your web page following the standard instructions here or the baseUrl instructions here.

If you would like to disable the drop-shadow on the main images in your gallery, then set imageShadowBlur="0" (in JuiceboxBuilder-Pro's 'Customize -> Main Image' section).

There is currently a bug which affects WebKit browsers (such as Chrome and Opera) whereby edited values are not saved. The bug will be fixed in the next version of WP-Juicebox but in the meantime, a quick and easy fix is to open the 'wp-juicebox/js/edit.js' file in a plain text editor and remove lines 9, 10 and 11:

jQuery('input', '#jb-edit-action, #jb-set-action').click(function() {
    jQuery('input', jQuery(this).parent()).prop('disabled', true);
});

This will not affect the functionality of WP-Juicebox.
Alternatively, you can edit a gallery from the 'Manage Galleries' page using either Firefox or Internet Explorer.

There are only two known bugs in the current version of WP-Juicebox and, as a Picasa Web Album and WebKit browser user, it is unfortunate that your scenario has uncovered both of them. Please be assured, though, that we aim to fix all known bugs

Your gallery certainly displayed OK when I tried it yesterday.
However, it does not seem to be working at the moment.
The problem seems to be with either the creation of the creation of the XML file on your web server or the fetching of the images URLs from your Picasa Web Album.
If I try to open your gallery's XML file (which is created dynamically by a PHP file) directly in a browser, the XML data is never displayed (although it displayed OK yesterday): http://malibu-gates.com/wp-content/plug … llery_id=2

Please try uploading this version of WP-Juicebox [File removed.] to your 'plugins' folder.
It contains fixes for both bugs (the Picasa Web Album not displaying at all and the inability to edit a gallery in WebKit browsers) and also bypasses a routine which checks the suitability of images returned by Picasa for a Juicebox gallery which should speed up the XML file creation process.
There is no 'jbcore' folder in this zip file so you can upload the entire contents to your 'plugins' directory (and allow it to overwrite all existing files) and it will not overwrite your current 'jbcore' folder.

You might also like to try creating a test gallery using the Picasa User Id "picasateam" and the Picasa Album Id/Name "VegasWeekend" (a small test Picasa Web Album with 14 images) to see if this displays OK.

@come_paglia

Yes. If you want to add common embedding code settings (stored in a file named 'extra.php'), then you can essentially follow the same procedure as above.

(1) Change the file extension of the page containing your gallery's embedding code from .htm or .html to .php.

(2) Use embedding code such as the following:

<!--START JUICEBOX EMBED-->
<script src="jbcore/juicebox.js" type="text/javascript"></script>
<script>
    new juicebox({
        containerId: "juicebox-container",
        <?php include 'extra.php'; ?>
    });
</script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->

(3) Your 'extra.php' file might look something like this:

galleryWidth: "600",
galleryHeight: "400",
backgroundColor: "rgba(255,255,255,1)",
stagePadding: '20',
useThumbDots: "TRUE"

Thank you for checking the demo galleries on your device.
I have notified the developers of both these issues and hopefully they will be fixed in a future version.

It looks like the first problem (the caption area spilling over outside the browser window) may be due to setting thumbNavPosition="BOTTOM" (in JuiceboxBuider-Pro's 'Customize -> Thumbnail' section) and the space required for the thumbnail navigation arrows below the thumbnails not being taken into account in the gallery layout. Try setting thumbNavPosition="CENTER" to see if this helps.
Another possible workaround until the bug is fixed might be to increase the maxCaptionHeight (in JuiceboxBuilder-Pro's 'Customize -> Caption' section).

With regard to the second problem  (the thumbnails increasing in size when closing an expanded gallery for a second time), could you perhaps take a couple of screenshots of our Simple demo gallery (before and after the issue occurs) to illustrate the problem. (I do not have Galaxy Pro 10.1 on which to test.) Thank you.
Unfortunately, I do not think that there is an easy workaround for this problem.