Closed beaudet closed 3 years ago
Note that the screenshot above shows the FIXED behavior. I didn't capture screenshots of the broken behavior, but instead of the map displaying in the slot, a small white square about 10x10 pixels is rendered instead of the image - this is purely browser / Mirador behavior as the unpatched IIP server returns HTML and a 400 Bad Request response rather than an actual image.
I've moved this issue over to our "new" repository for Mirador 2. Unfortunately, Mirador 2 is no longer well supported by the community and most of our efforts are on improving Mirador 3.
I can't tell from your report, but might this be an issue to pursue with OpenSeadragon (if they haven't already fixed it) or in the IIIF community.
Yeah, I figured that was probably the case. I'll try the manifest with Mirador 3 and see if it has similar behavior... or maybe someone already knows?
As far as I can tell using the demo M3, M3 doesn't request image sizes smaller than the smallest scale factor, e.g. "1,", "2,", "4,", "8,", etc. as M2 seems to do, so I don't think there's anything to fix in M3.
👍 ; openseadragon must have fixed something. I don't know what it'd take to update OSD here.
Observed behavior