Iabookreader with IIIF Manifest V3 fails to highlight when search term is passed via URL #445
Labels
bug
Something isn't working
Field Formatter
The thing that glues the pieces and adds glitter
IIIF
Specs/Manifests/Implementations
Javascript
Favourite language of a PHP developer
UX
Like UI but with an X
Milestone
What?
New to me.
Was testing the IABookreader behavior today and noticed that, when IIIF Manifest V3 with page/individual hints is loaded the URL fragment (
#search/someword
) is ignored. This does not happen on a Manifest V2.Not clear yet what/how this is happening but it might be related to how the default mode (the /mode/) is being added when a paging hint is found, not taking in account any previous passed /search. This is JS.
@alliomeria will ask to replicate. Kinda a biggie bc people love their highlights
Update. This happens not only on V3. It is related to how URL based manifests are being parsed (when using an exposed endpoint) and when that happens, how the https://github.com/internetarchive/bookreader/blob/master/src/plugins/plugin.resume.js plugin kicks in sooner replacing anything passed via a cookie content.
Options are:
I never liked the resume one to be honest....
The text was updated successfully, but these errors were encountered: