[DEPRECATED] An open-source, web-based 'multi-up' viewer that supports zoom-pan-rotate functionality, ability to display/compare simple images, and images with annotations.
Other
0
stars
2
forks
source link
Range with both ranges and canvases property causes problem #6
If I have I have a range that lists both the ranges that lie within it and the canvases that it contains, I notice an undesirable behavior in Mirador.
When you click on an item within the range question, the side bar panel will always scroll back up to the title for the parent range no longer allowing the user to see the item they just clicked on. See my attached Gif.
However, if you do not include the canvas property for range the behavior is improved, but if you click on the parent range itself you get the following error:
Uncaught TypeError: Cannot read property '0' of undefined
And Mirador will, obviously, not take you to the first canvas for this parent range. See the attached gif for behavior when canvases ARE listed.
If I have I have a range that lists both the ranges that lie within it and the canvases that it contains, I notice an undesirable behavior in Mirador.
When you click on an item within the range question, the side bar panel will always scroll back up to the title for the parent range no longer allowing the user to see the item they just clicked on. See my attached Gif.
However, if you do not include the canvas property for range the behavior is improved, but if you click on the parent range itself you get the following error:
And Mirador will, obviously, not take you to the first canvas for this parent range. See the attached gif for behavior when canvases ARE listed.