-
Notifications
You must be signed in to change notification settings - Fork 16
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
Miscellaneous editorial improvements. #895
Comments
If you're adding a note about the mandatory semantics of presentation processing including ISD construction and synchronic flow processing then please do also mention something equivalent to the text in §11.3.1:
|
I think this needs to say "neither specifies itself nor references a style that specifies" - presumably the "associated" wording was intended to accommodate either direct or referential specification of the |
We should disambiguate "animation element" from " |
The "if not possible" presumably applies to both sub-steps, not each individually. That is, if the first sub-step fails, do not go on and attempt the second sub-step. In that case, though, some of the _P_s will end up with a category that is not "computed". This needs to be noted, and I am not sure how a processor is supposed to deal with them. Does that mean those properties must be ignored for downstream presentation processing? Can they be used in transformation processing? It also means that the definition of the term "computed style set" now includes some styles that are not in fact computed, which is non-intuitive to say the least. Also, the wording is "the following ordered sub-steps". |
@nigelmegitt re:
Moved this task into #905.
No. It means does not specify (in this specific example code).
I've dealt with this specific issue (in context) by employing references to the [inline animation] term.
Actually, what I mean is do (a) if possible, then do (b) regardless of whether (a) was possible. The result will still be called a computed value, but if it were not possible to resolve (during this procedure) then it will be subject to further resolved computed value processing, about which see improvements to 10.4.3.2. |
Miscellaneous editorial improvements (#895).
is significant for the purpose of performing [construct anonymous
span]
further resolved at either layout or rendering time when (1)
such resolution is required by the semantics of a specific property
or the information required to perform the resolution is not
available until layout or rendering;
at reference points (see tts:lineHeight and possibly elsewhere);
conditionally included nested style element" or add note to this
effect;
animate
andset
elements;
each conditionally included immediate animation element" or add note
to this effect;
not possible, and that further value resolution may occur;
The text was updated successfully, but these errors were encountered: