Editorial improvements for 'content element' usage (#892). #899
Conversation
| @@ -1314,8 +1314,7 @@ abbreviated as <emph>ipd</emph> or <emph>IPD</emph>.</p> | |||
| <p>A <loc href="#terms-region">region</loc> that is defined in an inline manner with respect to some | |||
| <loc href="#terms-content-element">content element</loc> to be selected into (targeted to) the region. | |||
| An inline region is specified either explicitly by a <loc href="#layout-vocabulary-region"><el>region</el></loc> element child of | |||
| a <loc href="#terms-content-element">content element</loc> or implicitly by specifying a <loc href="#style-attribute-extent">tts:extent</loc> | |||
| or <loc href="#style-attribute-origin">tts:origin</loc> style attribute on a <loc href="#terms-content-element">content element</loc>. | |||
| certain <loc href="#terms-content-element">content elements</loc>. | |||
There was a problem hiding this comment.
Does this deletion come from another branch?
There was a problem hiding this comment.
No. The text "or implicitly ..." was removed because we no longer have implicit inline regions; rather, we have implied region animation. That is to say, we now only have explicit inline regions.
spec/ttml2.xml
Outdated
| @@ -16829,8 +16828,8 @@ defined to be coterminous with the <loc href="#terms-root-temporal-extent">root | |||
| <p>The <el>region</el> element is used to define a rectangular space or area into which content is | |||
| to be flowed for the purpose of presentation.</p> | |||
| <p>A <el>region</el> element may appear as either (1) a child of a | |||
| <loc href="#layout-vocabulary-layout">layout</loc> element or (2) a child of block level | |||
| <loc href="#terms-content-element">content element</loc>, specifically, of elements | |||
| <loc href="#layout-vocabulary-layout">layout</loc> element or (2) a child of certain block level | |||
There was a problem hiding this comment.
Why not just say (2) a child of an element in the <loc href="#element-vocab-group-block">Block.class</loc> element group ?
There was a problem hiding this comment.
Because image in a block context, e.g., child of div, is block level content element but is not a member of Block.class.
There was a problem hiding this comment.
But then the text on line 16832-3 that says "specifically, of elements in the Block.class element group" must change, right?
|
The Working Group just discussed The full IRC log of that discussion<nigel> Topic: Editorial improvements for 'content element' usage (#892). ttml2#899<nigel> github: https://github.com//pull/899 <nigel> Glenn: This is a small number of editorial improvements. <nigel> .. Nigel you have an outstanding comment I need to look at. <nigel> Nigel: Yes <nigel> Glenn: We can do this offline. <nigel> Nigel: Ok |
|
@nigelmegitt please re-review |
|
Merged early per WG resolution to move forward with CR3 CfC. |
Closes #892.