Re: CSS Charter (Apple's Wishlist)

As a longtime fly-on-the-wall, take this opinion however you'd like: as a long-time web developer, animations and transitions seem like something that could work with CSS but not necessarily as part of it. The WebKit implementation seems to make some simplifying assumptions, such that you'd only want to animate one property at a time. I'd much rather see a JavaScript-based API that allows me to specifying numerous properties, start and end values, as well as timing information. Putting this information solely in CSS seems very forced to me.

Just my two cents.

-Nicholas

----- Original Message ----
From: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
To: www-style@w3.org
Sent: Thursday, March 27, 2008 11:02:52 PM
Subject: Re: CSS Charter (Apple's Wishlist)


David Hyatt wrote:

> Here is a list from Apple regarding what we would like to see within the 
> scope of the CSS WG's charter.

Here's my personal (I insist: personal) take about your proposals, from
a pure CSS p.o.v.:

1. transformations change nothing in the behaviour or semantics of an
    element, it's strictly about rendering effects : in scope
2. transitions are even deeper than rendering, they affect the
    way a property value is applied to an element : in scope
3. animations are just a way to apply a set or continuum of various
    property values to an element : in scope
4. CSS Media Queries extensions ; of course in scope

That said, I am not saying anything about the solutions you chose, I am
just saying I have the personal feeling it's perfectly normal to ask the
CSS WG to deal with your proposals.
As a web author, I want these features and I want them as simple to edit
as possible. As a standards guy, I want to make sure (a) we're not
reinventing the wheel (b) we're not going to neglect the HUGE
experience other W3C WGs have on these topics [1] (c) it's intuitive
and simple enough so web authors can edit w/o having to hire an expert
to understand the spec. Point (c) is in my humble opinion already
ok.

[1] for instance on transition collisions...

</Daniel>
--
Co-Chair, W3C CSS Working Group











      ____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.  
http://tc.deals.yahoo.com/tc/blockbuster/text5.com
--0-232729560-1206940909=:39432
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">As a longtime fly-on-the-wall, take this opinion however you'd like: as a long-time web developer, animations and transitions seem like something that could work with CSS but not necessarily as part of it. The WebKit implementation seems to make some simplifying assumptions, such that you'd only want to animate one property at a time. I'd much rather see a JavaScript-based API that allows me to specifying numerous properties, start and end values, as well as timing information. Putting this information solely in CSS seems very forced to me.<br><br>Just my two cents.<br><br>-Nicholas<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Daniel
 Glazman &lt;daniel.glazman@disruptive-innovations.com&gt;<br>To: www-style@w3.org<br>Sent: Thursday, March 27, 2008 11:02:52 PM<br>Subject: Re: CSS Charter (Apple's Wishlist)<br><br>
<br>David Hyatt wrote:<br><br>&gt; Here is a list from Apple regarding what we would like to see within the <br>&gt; scope of the CSS WG's charter.<br><br>Here's my personal (I insist: personal) take about your proposals, from<br>a pure CSS p.o.v.:<br><br>1. transformations change nothing in the behaviour or semantics of an<br>&nbsp; &nbsp; element, it's strictly about rendering effects : in scope<br>2. transitions are even deeper than rendering, they affect the<br>&nbsp; &nbsp; way a property value is applied to an element : in scope<br>3. animations are just a way to apply a set or continuum of various<br>&nbsp; &nbsp; property values to an element : in scope<br>4. CSS Media Queries extensions ; of course in scope<br><br>That said, I am not saying anything about the solutions you chose, I am<br>just saying I have the personal feeling it's perfectly normal to ask the<br>CSS WG to deal with your proposals.<br>As a web author, I want these features and I
 want them as simple to edit<br>as possible. As a standards guy, I want to make sure (a) we're not<br>reinventing the wheel (b) we're not going to neglect the HUGE<br>experience other W3C WGs have on these topics [1] (c) it's intuitive<br>and simple enough so web authors can edit w/o having to hire an expert<br>to understand the spec. Point (c) is in my humble opinion already<br>ok.<br><br>[1] for instance on transition collisions...<br><br>&lt;/Daniel&gt;<br>--<br>Co-Chair, W3C CSS Working Group<br><br><br><br><br><br></div><br></div></div><br>
      <hr size=1>OMG, Sweet deal for Yahoo! users/friends: <a href="http://us.rd.yahoo.com/evt=47520/*http://tc.deals.yahoo.com/tc/blockbuster/text2.com
">Get A Month of Blockbuster Total Access, No Cost.</a> W00t</body></html>
--0-232729560-1206940909=:39432--

Received on Tuesday, 1 April 2008 15:23:56 UTC