W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2017

Re: [csswg-drafts] reconsider name of frames() timing function

From: Rachel Nabors via GitHub <sysbot+gh@w3.org>
Date: Tue, 16 May 2017 07:23:38 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-301698072-1494919417-sysbot+gh@w3.org>
I'd have an easier time explaining that "both" is the equivalent of start
AND end than inside and outside. But consider as well, "steps, none" seems
to read that there are no steps happening at all!
On Tue, May 16, 2017 at 4:03 PM Brian Birtles <notifications@github.com>

> Given issue #1371 <https://github.com/w3c/csswg-drafts/issues/1371>, I'm
> now more inclined towards extending steps(). I know we've had that
> conversation before, but since then two things have changed:
>    - There is interest in re-using this for gradient stops where frames()
>    seems like a less suitable name
>    - There is interest in a fourth variation on this theme where *neither*
>    of the endpoints are included
> In a sense, frames() ensures both endpoints get their fair portion of
> showtime, while issue #1371
> <https://github.com/w3c/csswg-drafts/issues/1371> seeks the opposite
> effect: neither endpoint gets a showing.
> These are really all variations on a theme so I feel like a common
> function name (or at least similar function names) makes sense.
> Unfortunately steps(n, start) means that the start value does *not* get a
> showing, otherwise I'd suggest the four keywords are: start, end, both, and
> none and they represent which endpoints are included (and we just accept
> the fact that the n is interpreted differently for 'both' and 'none').
> If we accept that the keyword represents where the vertical steps lie,
> then perhaps the keywords could be: start, end, inside, outside?
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/csswg-drafts/issues/1301#issuecomment-301684086>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAObEgEwAuI9sl19RwjsDqD0TPgLLqQ5ks5r6TwVgaJpZM4NJwYI>
> .

[image: photo]
*Rachel Nabors*
Web Animation Engineer
<http://twitter.com/rachelnabors>  <http://dribbble.com/rachelthegreat>

Curator of Web Animation Weekly <http://webanimationweekly.com>,
founder of Animation
at Work <http://slack.animationatwork.com>
*Best of 2016*

   - The Web in Motion
   - Alice in Web Animations API Land <https://vimeo.com/163510676> talk
   and MDN documentation
   - Web Animation Past, Present, and Future
   <http://alistapart.com/article/web-animation-past-present-and-future> *A
   List Apart* article
   - Career Offroading
   lightning talk
   - Communicating Animation
   <http://alistapart.com/article/communicating-animation> *A List Apart*

GitHub Notification of comment by rachelnabors
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1301#issuecomment-301698072 using your GitHub account
Received on Tuesday, 16 May 2017 07:23:46 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:12 UTC