- From: Glenn Adams via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Mar 2018 00:11:50 +0000
- To: public-tt@w3.org
skynavga has just created a new issue for https://github.com/w3c/ttml2: == Remove @style from set and animate. == On further consideration, I now have doubts about the utility of adding ``@style`` on ``set`` and ``animate`` elements. In the case of ``set``, the ``@style`` attribute was not supported in TTML1, and, further, only a single style attribute was permitted on ``set`` in TTML1. In TTML2, we now allow multiple style attributes on a single ``set``, but adding ``@style`` seems to go to far, particularly given the disparity with multiple values on ``animate``. In the case of ``animate``, the values of targeted style attributes will consist of multiple values, i.e., as ``<animation-value-list>`` expressions. While it is straightforward to recognize the possibility of multiple values on a style attribute that appears directly on an ``animate`` element, it is not at all straightforward to support multiple values on an attribute that appears on a ``style`` element directly or indirectly referenced via ``@style`` on ``animate``. In this case, we would have some ``style`` elements with multiple value styles (for reference by ``animate`` elements) and others with single value styles (for reference by other content and ``set`` elements). I propose that we back out the addition of ``@style`` on ``set`` and remove it from ``animate``. This will significantly reduce the complexity of implementations of animation elements without impacting functionality, since one can directly specify animated attributes on ``set`` and ``animate`` without use of ``@style``. Please view or discuss this issue at https://github.com/w3c/ttml2/issues/703 using your GitHub account
Received on Wednesday, 28 March 2018 00:11:55 UTC