-
Notifications
You must be signed in to change notification settings - Fork 62
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
Normatizing the fixed layout property statements #1936
Comments
Earlier in the revision we changed from Reading Systems must support the default value to the current prose without a normative keyword because it was said the statements weren't useful for auto values: #1313 The assertion cannot be failed, but that was always by design to allow the default behaviour of reading systems to pass. Are we okay with testing auto again? |
The issue was discussed in a meeting on 2021-12-09 List of resolutions:
View the transcript3. Normatizing the fixed layout property statements (issue epub-specs#1936)See github issue epub-specs#1936. Wendy Reid: i noticed that in RS spec we say in Dave Cramer: there are a couple instances where we say that the default value MUST be assumed, but i didn't know how that would be testable. Wendy Reid: the default behaviour is auto, and that means to respect what the RS is doing. Brady Duga: you could not specify in one case and specify in another case, and if the result is the same then the RS passes?. Wendy Reid: my proposal was to turn the 2x non-normative default behaviour statements into normative MUSTs. Dave Cramer: so we just ask mgarrish to made the change, then.
|
The Fixed Layout properties section of the RS spec makes a number of informative default statements for the various
rendition
properties, but only one of them is a normative statement.The default value statements for
rendition:orientation
andrendition:spread
are both informative (and the same).I would propose making these both normative MUST statements to match the statement made for
rendition:layout
and to clarify this section.The text was updated successfully, but these errors were encountered: