- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Jun 2020 14:20:55 +0000
- To: public-css-archive@w3.org
andruud has just submitted a new pull request for https://github.com/w3c/csswg-drafts: == [web-animations-1] Specify how to compute property values == When it comes to the term "computed value", the spec is currently very confused. It appears to be making several references to "the" computed value (as in [1]), when in reality the intention is (I believe) to apply the *process* that calculates the computed value ([1]) to the value specified (locally) in the keyframe. This process is not described in a reusable way anywhere (I think), so I've added the algorithm "compute a property value" for this. I'm using the term "property value", since it's already extensively used in this spec. Possibly it would be more suited for css-cascade, but I'm proposing it for this spec until we need it somewhere else. In general I want to maintain a clear distinction between when we mean the actual computed value [1], and when we mean some value that has undergone the "compute a property value" process. Hence, I think we should avoid referring to a value that has undergone the "compute a property value" process as "a" computed value, as it's too easily confused with *the* computed value. I've included some text and an examples that hopefully clarify the expected interpolation behavior a little bit. It seemed somewhat natural to place this in the "Computing property values" section, since resolving dependencies is part of the process when computing values. Fixes #5125. [1] https://drafts.csswg.org/css-cascade/#computed See https://github.com/w3c/csswg-drafts/pull/5255
Received on Tuesday, 23 June 2020 14:20:57 UTC