viewingHint, viewingDirection should be inherited from manifest if not on sequence

[tomcrane]

as per http://iiif.io/api/presentation/2.0/

examples:

http://universalviewer.io/examples/?manifest=http://www.qdl.qa/%D8%A7%D9%84%D8%B9%D8%B1%D8%A8%D9%8A%D8%A9/iiif/81055/vdc_100000004987.0x000001/manifest

(on manifest - ignored)

http://universalviewer.io/examples/?manifest=http://tomcrane.github.io/presentations/uv-ghent/rtl-manifest.json

(on sequence - observed) The latter is partly right - the thumbnail flow is correct in both views - but the < and > buttons don't follow the flow (and are incorrectly labelled).

If I read in Arabic I keep pressing [<] to page through in order. [<] means "next". To work it requires that the order of canvases in the sequence (in the json) is the natural reading order of the material, not the order the person who digitised it paged it out of habit.

Has this changed since implemented for the BL?

[tomcrane]

@edsilv This issue appears to have reverted to the previous behaviour for viewingHint only. The "paged" viewingHint on the manifest is being ignored (although the viewingDirection on the manifest is being observed). A manifest-level hint applies to all sequences, an individual sequence can override it.

[LlGC-szw]

All issues will be triaged for further investigation or closure by the 28 September 2023. If your issue is still relevant and would like for it be investigated further please comment by 14 September 2023.

[tomcrane]

This should be fixed if still an issue. Although it may become less of an issue as v3 manifests become more common that v2; v3 goes straight from manifest => items rather than have the intermediary sequence.