If you are looking for examples of Juicebox galleries, then you might like to check out our own demo galleries here.

We have also highlighted several other users' galleries in our Facebook page, our Twitter feed and our blog.

The easiest way to showcase a Juicebox gallery on the web would be to upload the complete gallery folder to a regular web server via FTP. You can then load the gallery's 'index.html' file in a browser to view the gallery.
Juicebox galleries can also be displayed in web template sites by following the instructions here.

Keyboard controls seem to work fine for me on the first image in your gallery as soon as the web page has loaded (in Chrome, Firefox and Internet Explorer on PC).
If the gallery is embedded in a web page alongside other content, then you would need to click on the gallery to give it focus before keyboard controls would work but this should not be necessary in a full page gallery (where the gallery's dimensions are 100% x 100% and it is the only content on the page).

Try completely clearing your browser's cache before reloading your web page to see if this helps.

To automatically give your gallery focus after the web page has loaded, 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: '100%',
        galleryHeight: '100%',
        backgroundColor: 'rgba(223,223,223,1)'
    });
    jb.onInitComplete = function() {
        $('#juicebox-container').find(':first-child').focus();
    };
</script>
<div id="juicebox-container"></div>

That's great! Thanks for letting me know.

According to your gallery's 'config.xml' file, the first image in your gallery should be located here: http://eye.de/gal-html5/marilena/images … _1000h.jpg
... but going directly to that location in a browser results in an error 403 (forbidden).

Please check that your thumbnail and image files have been uploaded to the correct locations on your web server and that their permissions (and the permissions of the 'thumbs' and 'images' folders themselves) are not too restrictive.
Default permissions of 755 for folders and 644 for files should be fine.

You can check and change permissions with an FTP program such as Filezilla or via your web hosting account's online file manager.

Also, please see this FAQ which may help:
My images show locally, but not when I upload them to my website. Why?

I have just tried embedding a gallery on Google Drive at less than 100% x 100% (at a fixed size of 600px x 400px) in a web page setting showSplashPage="ALWAYS" and trying both expandInNewPage="FALSE" and expandInNewPage="TRUE". The gallery expands correctly in both scenarios on my iOS device and in desktop browsers.
Here it is with expandInNewPage="AUTO":
https://7e149673cba79128b4d3fe7ac7a9b89 … index.html

I get an error 400 when trying to switch galleries on your web page (as well as when trying to expand a gallery from the Splash Page) so I think the problem might have something to do with the code on your web page and the way that your galleries are embedded or loaded.

As the problem happens when clicking one of your gallery links, you should have more control in debugging the switching of your galleries than the expanding of the Splash Page (although, being that the error messages are the same for both scenarios, they might be related to each other).

I would try debugging your web page's JavaScript code to ensure that all your variables are set as you expect them to be.
This should hopefully help to track down the cause of the problem.
After setting a variable but before using it, use a JavaScript alert box to check its value to see if it is what you expect it to be or if it is perhaps undefined for some reason (maybe due to a limitation in using Google Drive rather than a regular web server).
Check that everything is OK before running your new juicebox(content.options); line of code.

I would also try stripping back your custom JavaScript code so that only basic functionality exists.
You could then reintroduce elements, one at a time, to see if you can find the cause of the problem.

I realise that this does not directly solve your problem but I hope it at least points you in the right direction.

You might also like to look into the possibility of hosting your web site on a regular web server rather than on Google Drive.
Juicebox does not require any special server requirements so most web hosts (even those offering free web space) should be suitable.

Thank you for providing the URL to your test page.

I have done some further investigation and it looks like the problem may somehow be related to the meta viewport tag on your main page.

I have loaded a default full page gallery into an iframe which takes up 80% of the page's width (just an arbitrary value that is not 100% so that any problems can easily be seen).
On changing orientation and then changing it back, there is no resizing and the gallery always fills the iframe and the iframe always fills 80% of the page's width.
Here is the test gallery.

As soon as I introduce a meta viewport tag into the page, such as the one you use in your web page (below), there are resizing problems (not exactly the same as yours but resizing problems nonetheless).

<meta name="viewport" content="width=device-width, initial-scale=1">

I don't know if anything can be done from within the iframe page (the gallery) but one possible workaround would be to refresh the page when the orientation changes. This will reset the page layout each time the device's orientation is changed.
This can be achieved by adding the following JavaScript code on your web page:

<script>
    window.onorientationchange = function() {
        window.location.reload();
    };
</script>

This might not be an ideal fix but it should work.
(The best solution would probably be to embed the gallery directly into your web page and not use an iframe but I realise that this is not possible with a web template site such as Squarespace.)

You might find the following two forum threads interesting.
http://stackoverflow.com/questions/1080 … ion-change
http://stackoverflow.com/questions/7919 … ion-change

That's great. Thank you for letting me know.

That's because the gallery is embedded in a web page at 100% x 100% with no other content on the page.
The gallery is not actually embedded into your main page. The gallery is embedded into the page which is loaded into your iframe. (This is the page which contains the gallery's embedding code.)
The Splash Page is displayed only when a gallery is embedded in a web page at less than 100% x 100% (or if showSplashPage="ALWAYS").

The best thing to do would be to post your suggestion in the Feature Requests forum thread.
This keeps all the ideas together and ensures that they are not overlooked by the developers.
Thank you.

Please note that we did not write the Juicebox module for Drupal ourselves and if you have any queries relating directly to the module, I would recommend that you post in the Drupal forum where the author of the module (who will be more familiar with both Drupal and the module itself) should be able to help you out further: https://www.drupal.org/forum
The Juicebox module for Drupal is an unofficial plugin but is well supported by its author on the Drupal forum.

Also, the link you provided points towards an alpha (pre-beta) version of the module so there may well be bugs in it.
If you find any, I'm sure the author of the module would be very grateful to know about them so that they can be tracked down and fixed.

Having said that, your problem sounds likely to be related to either the location of the Juicebox files on your web server or the permissions of the files (or parent folders).
Please double-check that you have uploaded the contents of the 'jbcore' folder to the correct location on your web server, step #3 in the instructions here: https://www.drupal.org/node/2000300
Copy the contents of the 'jbcore' folder (not the 'jbcore' folder itself) into the '/sites/all/libraries/juicebox/' folder on your web server.

Also, make sure that the permissions of the files and folders in the path are not too restrictive.
Default permissions of 755 for folders and 644 for files should be fine.

I realise that this may not directly solve your problem but I hope this points you in the right direction.

All Juicebox gallery files should be on the same domain (or subdomain) as the web page which contains the gallery's JavaScript embedding code due to the same-origin policy.
Please see here for details: https://developer.mozilla.org/en-US/doc … gin_policy

In order to use files on a different domain, you could implement a Cross-Origin Resource Sharing (CORS) solution. More information about CORS can be found here: http://www.w3.org/TR/cors/

If you have an Apache server, add the following line of code to the .htaccess file in the root directory of the domain which hosts the gallery folder.

Header add Access-Control-Allow-Origin "*"

If you have an IIS server, then please see this link for a similar solution: http://enable-cors.org/server_iis7.html

The problem you are encountering is likely to be due to captionPosition being used only in Large Screen Mode (and not in Small Screen Mode). (This is noted in the description for the option in the Caption Options section of the Config Options page.)
In Small Screen Mode, captionPosition will always be set to its default value of OVERLAY_IMAGE.

There is much less screen real estate on a mobile device and for the caption text to be legible, it might take up too much space if it has an area of its own.

You could either:
(1) Set a captionBackColor and captionBackTopColor so that the caption can clearly be seen when it is overlaid on top of the image.
... or:
(2) Set screenMode="LARGE" so that the gallery is displayed in Large Screen Mode on all devices and in all browsers (so that all Large Screen Mode options are used).

Please note that priority is given to the main image rather than the caption text.
A long caption may be truncated if the maxCaptionHeight is not large enough. (A long caption will not push the main image up the screen resulting in the image being scaled smaller.)

Thank you for the suggestion.
I recommend that you 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.
Thank you.

Check the permissions of your gallery's XML file (and all its parent folders) on your web server to see if maybe they are too restrictive (which might prevent new entries from being written to the file).
Default permissions of 755 for folders and 644 for files should be fine.

If the permissions are fine, then I think Ryan over in the Drupal forum might be the best source of help. As the author of the module, he will be much more familiar with its code and functionality than I am.

If I think of anything else which might help, I'll be sure to post back here.