The UI worker proposal in the houdini TF has evolved into something else: https://docs.google.com/document/d/1xhuwlwdoqox3Fo3e4zFltgSGnbtMb-ptTYNx1loqPXU/edit#heading=h.f6va9m4yz8xn (which currently has a name that nobody likes). But they're moving towards a model where there's a compositor callback that can manipulate transform, opacity, and scroll position for a set of elements on the compositor thread, with those changes sent both onward and back to the main thread. It can be set up to be called when certain things change, and to return true to say it should be called back unconditionally for the next frame whether or not they change.
I'm not sure how clear the document itself is; I got a bit more context in the meeting; minutes at: http://logs.csswg.org/irc.w3.org/houdini/2015-08-29/#e589556 Feedback is probably best sent to the https://lists.w3.org/Archives/Public/public-houdini/ mailing list. -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
signature.asc
Description: Digital signature
_______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
