ISSUE-176: Adding support for extent and origin attributes on block elements
extent and origin on blocks
Adding support for extent and origin attributes on block elements
- State:
- OPEN
- Product:
- TTML.next
- Raised by:
- Sean Hayes
- Opened on:
- 2012-08-23
- Description:
- It has become common practice to use the extent and origin attributes directly on block elements (specifically <p>), as this greatly simplifies authoring and conversion process. This is essentially akin to creating 'anonymous' regions for each block, or relative positioning in CSS.
The TTML 1.0 spec allows this syntactically but did not specify any meaning. We should resolve this by supplying reference semantics for the practice. - Related Actions Items:
- ACTION-66 on Sean Hayes to Create ISSUE regarding use case / requirement for specifying extent and origin on content element, such as tt:p - due 2012-05-31, pending review
- ACTION-73 on Sean Hayes to Incorporate result of ACTION-71 into CP http://www.w3.org/wiki/TTML/changeProposal002 - due 2012-07-19, pending review
- Related emails:
- RE: TTML Agenda for 15/05/13 (from mdolan@newtbt.com on 2013-05-15)
- RE: ISSUE-176 (extent and origin on blocks): Adding support for extent and origin attributes on block elements [DFXP v.next] (from mdolan@newtbt.com on 2012-09-07)
- Re: TTML Agenda for 6/9/12 (from geoff_freed@wgbh.org on 2012-09-06)
- TTML Agenda for 6/9/12 (from Sean.Hayes@microsoft.com on 2012-09-06)
- RE: [minutes] 20120823 TTML (from momartin@microsoft.com on 2012-08-23)
- [minutes] 20120823 TTML (from plh@w3.org on 2012-08-23)
- ISSUE-176 (extent and origin on blocks): Adding support for extent and origin attributes on block elements [DFXP v.next] (from sysbot+tracker@w3.org on 2012-08-23)
Related notes:
No additional notes.
Changelog:
Created issue 'Adding support for extent and origin attributes on block elements' nickname extent and origin on blocks owned by Sean Hayes on product DFXP v.next, description 'It has become common practice to use the extent and origin attributes directly on block elements (specifically <p>), as this greatly simplifies authoring and conversion process. This is essentially akin to creating 'anonymous' regions for each block, or relative positioning in CSS.
The TTML 1.0 spec allows this syntactically but did not specify any meaning. We should resolve this by supplying reference semantics for the practice.' non-public
Status changed to 'open'
Monica Martin, 30 Aug 2012, 16:26:11