ISSUE-422: Presented region + itts:forcedDisplay
Presented region + itts:forcedDisplay
- State:
- CLOSED
- Product:
- TTML IMSC 1.0
- Raised by:
- Glenn Adams
- Opened on:
- 2015-09-21
- Description:
- Should the definition of 'presented region' account for the semantics of itts:forcedDisplay?
- Related Actions Items:
- No related actions
- Related emails:
- {minutes} TTWG Meeting 2015-10-15 (from nigel.megitt@bbc.co.uk on 2015-10-15)
- {agenda} TTWG Meeting 2015-10-15 (from nigel.megitt@bbc.co.uk on 2015-10-14)
- IMSC 1 issues (from nigel.megitt@bbc.co.uk on 2015-10-08)
- RE: {agenda} TTWG Meeting 2015-10-08 (from mdolan@newtbt.com on 2015-10-08)
- {agenda} TTWG Meeting 2015-10-08 (from nigel.megitt@bbc.co.uk on 2015-10-07)
- {agenda} TTWG Meeting 2015-10-01 (from nigel.megitt@bbc.co.uk on 2015-10-01)
- {agenda} TTWG Meeting 2015-09-24 (from nigel.megitt@bbc.co.uk on 2015-09-23)
- Update re: outstanding IMSC1 issues (from pal@sandflow.com on 2015-09-21)
- ISSUE-422: Presented region + itts:forcedDisplay [TTML IMSC 1.0] (from sysbot+tracker@w3.org on 2015-09-21)
Related notes:
I would think that the definition of 'presented region' should not account for the semantics of itts:forcedDisplay since the document should be conformant regardless of the value of 'displayForcedOnlyMode'.
Pierre-Anthony Lemieux, 21 Sep 2015, 17:56:45It's already included indirectly because itts:forcedDisplay effectively overrides the value of tts:visibility and tts:visibility is included in the definition of "presented region".
What is not clear is if the computed value of tts:visibility that applies to "presented region" is pre- or post- the itts:forcedDisplay override.
Display change log
