Nicolas Franck

Maybe this [line](https://github.com/ruven/iipsrv/blob/master/src/IIIF.cc#L393): ``` requested_width = region[2]; requested_height = region[3]; ``` should be ``` requested_width = width; requested_height = height; ``` at least if `width` and `height` keep being equal...

Mm, I also see that `region` is not handled everywhere in the same way. With `full` and `square` it is handled as if it always contains a value between `0`...

Thanks!

Riiif gives a deprecation warning during an upload to /upload_resources: ``` DEPRECATION WARNING: Initializing a file resolver without setting the base path is deprecated and will be removed in Riiif...

I understand, but in that case the panel becomes too wide. If you set the option `panelExpandedWidth` to a smaller value, then it becomes a problem for manifests where the...

ok

So am I ;-) v2.0.1 is what was reported in bower.json. But I'm sure this is about v3.

@rafaeluriarte it's a problem in the specification of IIIF: it treats the first canvas as the cover, and there is no way to circumvent this. If your first canvas happens...

The problem is that such a solution would only work here, in the UV, completely discarding the purpose of IIIF: interoperability..

apparently already implemented by @edsilv in https://github.com/IIIF-Commons/manifold/commit/6b3b8433a338cec38ba77dfdf6a4b43d7f61387f