-
Notifications
You must be signed in to change notification settings - Fork 56
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
inheritance of behaviors across resources #1612
Comments
Yes, that's all correct. We should be clearer in the spec text that |
A notion of overriding inheritance would, I think, end up with a need to have opposites or complete sets of alternate behaviors including the default. For example, in order to override |
If i being playing a temporal range set to auto-repeat (say a TOC), and then I click into the thumbnail-nav to go to a section (AKA the scrubber), but I have not set the thumbnail-nav range to be auto-repeat, does that viewer then cancel the auto-repeat behavior since I've selected a content resource from another enclosing resource? |
Eds call -
Then we need to specify sets of disjoint behaviors, and define any negation behaviors needed. |
Initial issue -- if Canvases do not inherit from Ranges, then it seems pointless to have Unordered, Individuals, Continuous and Paged on Ranges. The canvas would always inherit the value from the Manifest, not from the Range. This is the same sort of issue as auto-advance on a Range (#1632) ... it's the presentation of the canvases in the range that matters. |
|
More weirdness notes - If a newspaper article Range is part of a |
Closed by #1681 |
In presentation 2, as a viewer, if I come across a manifest with a
viewingDirection
, I should take that as an intention for the canvases to be displayed accordingly, even if there are multiple sequences. If multiple sequences, each with differentviewingDirection
properties, they trump the ManifestsviewingDirection
.In a way, sequences by default inherit the
viewingDirection
from the Manifest. Is this true for ranges? If a top level Manifest has aviewingDirection
ofright-to-left
, should that be inherited by each of the Ranges (if they don't have aviewingDirection
themselves) or should they default toleft-to-right
.Further, in presentation 3, if sequences are now represented as Ranges, their behaviour here will change, and any conversion between presentation 2 and presentation 3 would have to explicitly set the viewing direction, if it was previously implied by the Manifest having the property (if Ranges should not inherit this direction).
The text was updated successfully, but these errors were encountered: