IIIF/iiif-stories

As a user, I want it to work if I paste a full viewer+content-state URI into a viewer

zimeon opened this issue · 1 comments

zimeon commented

Description

The Content State API describes content states being pasted into viewers and also describes URIs that pass content state to a specific viewer using the iiif-content parameter (e.g. https://site/viewer.html?iiif-content=base64stuff in ). As a user (who likely doesn't know the detail in the sentence above) I might try to paste the full viewer URI into the same or another view and I would like it to "just work".

Proposed Solutions

Expand description of paste behavior to include extracting the iiif-content parameter from the full viewer URI like https://site/viewer.html?iiif-content=base64stuff. Consider whether this applies to any of the their mechanisms too. Also consider whether the combination of handling unencoded JSON, base62 encoded JSON, a plain manifest URI, or a full viewer URI might require a suggested algorithm for parsing.

mprove commented

ok, works fine for Chronoscope Word