Skip to content
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.

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

Range with both ranges and canvases property causes problem #6

Open
jeffreycwitt opened this issue Apr 16, 2016 · 3 comments
Open

Range with both ranges and canvases property causes problem #6

jeffreycwitt opened this issue Apr 16, 2016 · 3 comments

Comments

@jeffreycwitt
Copy link
Contributor

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.

mirador-toc-bug2

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.

mirador-toc-bug1

@rsinghal
Copy link
Contributor

this is related to ProjectMirador/mirador#248

@rsinghal
Copy link
Contributor

rsinghal commented May 4, 2016

Is the manifest on a public URL? We want to use it for testing.

@jeffreycwitt
Copy link
Contributor Author

Yep, try this:

http://scta.info/iiif/wdr-wettf15/manifest

@cbeer cbeer transferred this issue from ProjectMirador/mirador Jun 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants