ISSUE-258: extent value auto, potential conflict with css

extent value of auto

extent value auto, potential conflict with css

State:
CLOSED
Product:
TTML 1.0
Raised by:
Sean Hayes
Opened on:
2013-06-19
Description:
The current text specifies that for extent (which maps to width and height)

"If the value of this attribute is auto, then the initial value of the style property must be considered to be the same as the extent of the Root Container Region."

I'm not sure if this is what XSL:FO would do, but this behavior conflicts with the value auto in CSS, which works in concert with top, bottom, left and right to satisfy the constraint that, for example (ignoring margin etc for now):

'left' + 'width' + 'right' = width of containing block

If only origin is given we have the situation that both width and right would be auto, which according to CSS would give: width = shrink-to-fit and solve for 'right'

This in my mind would actually be much more useful behavior than the current specified behavior (although is a breaking change), especially in the case where origin is non zero.


shrink-to-fit width is: min(max(preferred minimum width, available width), preferred width).

If we don't do this, at minimum we have to have some rules here that explain why right, bottom should not be considered to have default = auto (but presumably zero in this case)

But my preference would be to adopt the shrink to fit concept when width/height is auto. I also believe we should consider extending extent to allow optional additional values to set right and bottom.

If we want to preserve the existing behavior for backwards compat, we might consider some kind of parameter that allows the setting of the assumed right position, this would also help with line-stacking etc too.
Related Actions Items:
No related actions
Related emails:
  1. [minutes] Timed Text 20130725 (from plh@w3.org on 2013-07-25)
  2. TTML Agenda for 25/07/13 (from Sean.Hayes@microsoft.com on 2013-07-25)
  3. Minutes - 2013-07-11 (from glenn@skynav.com on 2013-07-11)
  4. RE: TTML Agenda for 11/07/13 (from Sean.Hayes@microsoft.com on 2013-07-11)
  5. TTML Agenda for 11/07/13 (from Sean.Hayes@microsoft.com on 2013-07-10)
  6. RE: TTML Agenda for 26/06/13 (from mdolan@newtbt.com on 2013-06-27)
  7. TTML Agenda for 26/06/13 (from Sean.Hayes@microsoft.com on 2013-06-27)
  8. Re: TTML 1.0 Issues - Newly Moved to Pending Review (from glenn@skynav.com on 2013-06-20)
  9. Re: TTML 1.0 Issues - Newly Moved to Pending Review (from glenn@skynav.com on 2013-06-20)
  10. RE: ISSUE-258 (extent value of auto): extent value auto, potential conflict with css [TTML 1.0] (from Sean.Hayes@microsoft.com on 2013-06-19)
  11. Re: ISSUE-258 (extent value of auto): extent value auto, potential conflict with css [TTML 1.0] (from glenn@skynav.com on 2013-06-19)
  12. RE: ISSUE-258 (extent value of auto): extent value auto, potential conflict with css [TTML 1.0] (from Sean.Hayes@microsoft.com on 2013-06-19)
  13. Re: ISSUE-258 (extent value of auto): extent value auto, potential conflict with css [TTML 1.0] (from glenn@skynav.com on 2013-06-19)
  14. ISSUE-258 (extent value of auto): extent value auto, potential conflict with css [TTML 1.0] (from sysbot+tracker@w3.org on 2013-06-19)

Related notes:

Fixed. https://dvcs.w3.org/hg/ttml/rev/70165fde28e1 (see 9.3.3 step 5)

Glenn Adams, 20 Jun 2013, 04:45:53

Display change log ATOM feed


David Singer <singer@apple.com>, Nigel Megitt <nigel.megitt@bbc.co.uk>, Chairs, Thierry Michel <tmichel@w3.org>, Philippe Le H├ęgaret <plh@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.323 2013-12-19 14:47:09 dom Exp $