On the DM2 staging instance, visit the following project with an image known to previously be broken on iOS:
[x] Project: iOS Test Project, the specific image is PsalterListMapReallyBig
[x] The image should be working as usual on PC
[x] Open the page on an iOS device (iPhone, iPad) and confirm all images in the project can be viewed, including PsalterListMapReallyBig
It may take some time to load the largest two (Psalter and Elevation)
Also, on mobile you have to collapse the sidebar with the hamburger menu icon in the top left in order to actually view the images you've opened (not sure about tablet)
Description from Martin:
All images display fine on desktop browsers.
In iOS, images that do not display do so consistently in Chrome and Safari across all three platforms (see below)
I have tested this on a range of iOS devices - my newer iPad (iPad Pro 4th Gen, iOS v. 16.3.1) my iPhone (iPhone SE2020, iOS 17.2.1), and an older iPad (6th gen) running 17.3.1. All the images display or do not display consistently. The issue has been ongoing for at least a year if not more, so it appears operative across all iOS devices and systems, at least that I have seen.
The display or not display is consistent to specific sets of images - that is - images all from the same source - so for instance ALL Paris Psalter images do not load, yet ALL Vercelli Book images do. In the Exeter Book folder, older Exeter Book images load, but a different set we began to use in the middle of the project do not display.
This is an issue with local file uploads - IIIF image serving appears to be working. Images that do not display still have their thumbnail images display in folders, etc.
I don't think it has to do with file size or memory - given the differences of devices - but I cannot say for sure about that.
That's all I have - if you want versions of any of the original image files uploaded for analysis, I can probably provide those too - though I imagine you might just pull those off the image server.
[Warning] Canvas area exceeds the maximum limit (width * height > 16777216).
[Error] Unable to get image data from canvas because the canvas has been tainted by cross-origin data.
The former error indicates it is that bug (though the latter one indicates there could be something else going on here too).
testing notes (QA)
On the DM2 staging instance, visit the following project with an image known to previously be broken on iOS:
Description from Martin:
All images display fine on desktop browsers.
In iOS, images that do not display do so consistently in Chrome and Safari across all three platforms (see below)
I have tested this on a range of iOS devices - my newer iPad (iPad Pro 4th Gen, iOS v. 16.3.1) my iPhone (iPhone SE2020, iOS 17.2.1), and an older iPad (6th gen) running 17.3.1. All the images display or do not display consistently. The issue has been ongoing for at least a year if not more, so it appears operative across all iOS devices and systems, at least that I have seen.
The display or not display is consistent to specific sets of images - that is - images all from the same source - so for instance ALL Paris Psalter images do not load, yet ALL Vercelli Book images do. In the Exeter Book folder, older Exeter Book images load, but a different set we began to use in the middle of the project do not display.
This is an issue with local file uploads - IIIF image serving appears to be working. Images that do not display still have their thumbnail images display in folders, etc.
I don't think it has to do with file size or memory - given the differences of devices - but I cannot say for sure about that.
That's all I have - if you want versions of any of the original image files uploaded for analysis, I can probably provide those too - though I imagine you might just pull those off the image server.
And here's the starting point:
this may be a case of this OpenSeadragon bug, as we're getting these errors:
[Warning] Canvas area exceeds the maximum limit (width * height > 16777216). [Error] Unable to get image data from canvas because the canvas has been tainted by cross-origin data.
The former error indicates it is that bug (though the latter one indicates there could be something else going on here too).