-
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
Issue 0296 inline block #297
Conversation
Please don't merge just yet - I will review this in the next couple of days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks mostly good, a few tweaks:
-
In the table for
tts:textAlign
, in the Inherited row, it says "See prose". It would be helpful to say "Yes for p, No for span - See prose". -
The example for
tts:textAlign
needs to be updated to settts:display="inlineBlock"
on thespan
elements wheretts:textAlign
is set. This example should be referenced also in a note in the section ontts:display
because it provides a useful example of where the attribute is used. -
One typo as described in a comment.
spec/ttml2.xml
Outdated
to a <loc href="#content-vocabulary-span"><el>span</el></loc> element, then | ||
<loc href="#terms-inline-block-display">inline block display</loc> semantics apply and the element | ||
is a candidate for region layout and presentation. Furthermore, it is considered an error if the | ||
<code>inlineBlock</code> value to applied to any element which is not a <loc href="#content-vocabulary-span"><el>span</el></loc> element.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: s/to applied to/is applied to.
A question: do the sections on |
Address comments, except the first comment, which violates the DRY principle.
See #296 and #146.