You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In P3 spec the paged behavior is "Valid on Collections, Manifests and Ranges..." (not individual canvases; one canvas can't be paged)
facing-pages and non-paged are valid only on Canvases; they mark an individual canvas as an exception to the behavior of the parent sequence (lower case S).
But...
facing-pages says "Disjoint with paged and non-paged."
and
non-paged says "Disjoint with paged and facing-pages."
...the spec shouldn't say they are disjoint with paged when paged is not permitted on a Canvas, and these two behaviors are only permitted on Canvases.
The text was updated successfully, but these errors were encountered:
I agree, it is true in the sense that they can't be used on the same resource, but irrelevant because of that. This description could be fixed in a bugfix release because it isn't changing the spec
In P3 spec the
paged
behavior is "Valid on Collections, Manifests and Ranges..." (not individual canvases; one canvas can't bepaged
)facing-pages
andnon-paged
are valid only on Canvases; they mark an individual canvas as an exception to the behavior of the parent sequence (lower case S).But...
facing-pages
says "Disjoint withpaged
andnon-paged
."and
non-paged
says "Disjoint withpaged
andfacing-pages
."...the spec shouldn't say they are disjoint with
paged
whenpaged
is not permitted on a Canvas, and these two behaviors are only permitted on Canvases.The text was updated successfully, but these errors were encountered: