- From: Sean Hayes <Sean.Hayes@microsoft.com>
- Date: Sun, 19 Apr 2009 15:36:24 +0100
- To: Timed Text Working Group WG <public-tt@w3.org>
It occurs to me also that by the same argument, there is no reason that attributes like @region and @style could not also be animatable, (it which might even give motivation for the inherit value). e.g.: <p begin="1s" dur="3s" region="ordinaryCaption"> <set begin="2s" dur="1s" region="offsetCaptionLeft"/>Phrase being interrupted</p> <p begin="2s" dur="2s" region="offsetCaptionRight"> <set begin="1s" region="ordinaryCaption "/>Interrupting phrase</p> In such a case, it might be useful to be able to override a local style to the inherited value, but where one might not know what the currently applicable inherit was. Just a thought. Sean Hayes Media Accessibility Strategist Accessibility Business Unit Microsoft -----Original Message----- From: public-tt-request@w3.org [mailto:public-tt-request@w3.org] On Behalf Of Timed Text Working Group Issue Tracker Sent: 19 April 2009 1:42 PM To: public-tt@w3.org Subject: ISSUE-59: inconsistencies regarding animatability of style properties [DFXP 1.0] ISSUE-59: inconsistencies regarding animatability of style properties [DFXP 1.0] http://www.w3.org/AudioVideo/TT/tracker/issues/59 Raised by: Glenn Adams On product: DFXP 1.0 properties tts:direction tts:displayAlign tts:dynamicFlow tts:extent tts:origin tts:overflow tts:unicodeBidi tts:writingMode are not defined as animatable, and no rationale for lack of animatability is described; to simplify animation model, i propose to make all style properties animatable
Received on Sunday, 19 April 2009 14:35:12 UTC