Re: [csswg-drafts] [css-timing] Names for keyword arguments to steps timing function

Related to #136, #1371, and #1301.

At the F2F today, we resolved to accept both of the new "step-like" values: showing both the start and end values during the duration (original use-case for `frames()` in #136), and showing neither start nor end values during the duration (use-case from gradient transitions in #1371).  We also resolved that all of these would be done with the `steps()` function, and that the numeric argument would describe the number of values shown during the duration/iteration.  (That is, in Brian's diagram in <https://github.com/w3c/csswg-drafts/issues/1301#issuecomment-310571203>, the numeric arguments will be 3, 3, 4, and 2.)

During the meeting we couldn't come up with good keywords for these two new values, tho.  This thread is to address that issue.

There are two families of suggestions:

1. If we keep the existing `start` and `end` keywords as they are, they are interpreted as "don't show the start value" and "don't show the end value", respectively. The other two values thus need a "dont' show both" and "do show both" naming scheme.

2. Ignore the existing `start`/`end` keywords; assume we'll mark them as legacy keywords. Instead come up with a brand new set of four keywords that work well together.

Either way, we have to account for the fact that a *lack* of a keyword still default to `end` behavior. This means we can't, for example, use `drop-start || drop-end`, with the absence meaning the `frames()` behavior.

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1680#issuecomment-319723265 using your GitHub account

Received on Wednesday, 2 August 2017 16:19:36 UTC