Thank you so much for going to the trouble of posting screenshots (and for persevering with the forum software to do so!).
It is very interesting to see the cross that you are talking about.
It is curious to see that the cross and its background are not the same size as the Juicebox Back Button.
I suspect that the cross is actually covering up the Juicebox Back Button rather than replacing it.
Unfortunately I cannot update iOS on my old iPad 2 to test my theory but I suspect that the cross might actually be a feature of a later version of iOS on the iPad.
When you expand your gallery from the Splash Page, your gallery expands to fill the entire viewport, using the Fullscreen API (your gallery sets useFullscreenExpand="TRUE").
It looks to me like the cross might be Mobile Safari (on iPad only) presenting a way for the user to exit fullscreen mode.
This would explain why you do not see the cross in our demo galleries (they are not fullscreen, just full browser) and why I do not see the cross on my own iPad (it's too old).
It does not look like a coding fault (everything looks OK as far as I can tell) or even a fault of any kind. The cross looks intentional, like it's meant to be there (rather than an indication that something is wrong).
If my theory is correct, then if you set useFullscreenExpand="FALSE", you'll not see the cross.
https://dgrin.com/discussion/265876/ipa … e-x-button
Unfortunately, I've not found a way to disable the cross. (I'm not sure it's possible.)
It looks like the best course of action would be to either keep your BackButton centered or set useFullscreenExpand="FALSE".
Just to clarify a couple of your other points (which might now be somewhat redundant)...
I suppose that I could strip iOS completely from my iPad and get a fresh Install from Apple (if that is even possible?); and then re-install all of my personal data from a Back-up?
Yes. You can download the relevant iOS images from https://ipsw.me
The downloads come directly from Apple's update servers. (You'd need to back up your personal data first and it's a long process... not just a quick 5-minute job.)
You'll not need to do this, though. (It won't make a difference.)
I have just noticed something in my html coding which might be upsetting Safari:
I had TWO Head sections in the file!
It is certainly a good idea to fix any HTML errors in your web pages.
Some browsers may be less tolerant towards errors than others and a web page whose code validates correctly will be displayed with greater consistency and predicability across different browsers.
You can check your code with the W3C Markup Validation Service (and then fix any errors reported).