New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump mirador to use openseadragon 3.0.0 or latest (bug of current osd render limited-bound image using max) #3569

Closed

rainlemon opened this issue Sep 7, 2022 · 0 comments · Fixed by #3635

Labels

manifest compatibility

Milestone

rainlemon commented Sep 7, 2022

I am the author or maintainer of this manifest: Yes
URL: https://libraryimage.nga.gov/manifest/ic/99416073804896-new.json
Manifest hosting institution : National Gallery of Art Library

Observed behavior

Description: The manifest is loaded correctly , but the image 8,9,10 is not rendered due to the limited/allowed bounds.
It seems that Mirador 3.0 now uses the "max" syntax rather than "full", when communicating with a IIIF 2.0 compliant image server.
After digging into this issue with our IT, this is a known issue in current mirador using openseadragon 2.4.2 (ticket link , this bug has already been fixed by OSD 3.0.0 ticket link

So we are inquiring bumping OSD to 3.0.0 or latest for Mirdaor.

Thank you

rainlemon added the manifest compatibility label

cbeer added this to the v3.next/v4 milestone

cbeer mentioned this issue

Allow OSD 3.x and 4.x #3635

Merged

marlo-longley closed this as completed in #3635

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment