Re: [css-houdini-drafts] Proposal, custom script based transitions

Hi vidhill,

It’s true that the current CompositorWorker API does not allow you to 
assign behaviors via CSS, and your proposal certainly does make this 
possible. The customization of transitions is interesting, in 
particular.

That said, our current API is just a stand-in and we intend to change 
the API to be more Houdini-like in the near future. I’d presented 
[sketches of what this might look 
like](https://docs.google.com/document/d/1xhuwlwdoqox3Fo3e4zFltgSGnbtMb-ptTYNx1loqPXU/edit#heading=h.6enhp7h6oycq)
 last year, and some have similarities to your proposal.

But even this is still a work in progress -- we’re hoping make our 
first concrete API proposal shortly. In addition to the single element
 property animation that your approach permits, with our upcoming 
AnimationWorklet proposal we will be trying to address a bit of a 
wider variety of use cases:

- We would like to operate on more than one element at once (imagine 
some UI elements attached via springs and struts, eg).

- We would like to modify more than one property in a single 
invocation of the JS update function rather than emitting a single 
time fraction, and

- We would like to be able to gather information and send it back, 
asynchronously, to the main thread (consider implementing 
IntersectionObserver on top of this feature).


-- 
GitHub Notification of comment by ianvollick
Please view or discuss this issue at 
https://github.com/w3c/css-houdini-drafts/issues/269#issuecomment-236389385
 using your GitHub account

Received on Saturday, 30 July 2016 20:53:25 UTC