image-validator Test max functionality

Test the max properties to see if an image is returned which is outside of the allowed bounds:

https://iiif.io/api/image/3.0/#52-technical-properties

This would be an optional test and wouldn't necessarily use the test image.

Aug 16 '19 23:08 glenrobson

This issue was created over 3 years ago. It seems that Mirador 3.0 now uses the "max" syntax rather than full, even when communicating with a IIIF 2.0 compliant image server. Bumping this test for "max" syntax up in priority and releasing an updated version of the validator here: https://iiif.io/api/image/validator would be most helpful as "max" is clearly part of the last 2.x specification.

Sep 06 '22 17:09 beaudet

For info I think this is a bug in Openseadragon bug report which has been fixed in OSD 3.0.0. I believe Mirador is currently using 2.4.2.

Sep 07 '22 11:09 glenrobson

Thanks, sounds like a new Mirador bug report needs to be filed - I didn't find any existing tickets about this with M3 although it would seem to suggest that M3 won't work with image servers that don't support the "max" parameter.

Sep 07 '22 13:09 beaudet