W3C home > Mailing lists > Public > public-houdini@w3.org > February 2015

Re: Why we need Houdini...

From: François REMY <francois.remy.dev@outlook.com>
Date: Wed, 11 Feb 2015 18:07:49 +0000
Message-ID: <DUB405-EAS135D7C075969C555D138AB8A5250@phx.gbl>
To: Rick Byers <rbyers@chromium.org>, Greg Whitworth <gwhit@microsoft.com>
CC: "public-houdini@w3.org" <public-houdini@w3.org>
How close is that from https://wiki.css-houdini.org/background ?

Shouldn’t we merge them and create (sub-)categories? Add longer descriptions?

De : Rick Byers
Envoyé : ‎mercredi‎ ‎11‎ ‎février‎ ‎2015 ‎04‎:‎58
À : Greg Whitworth
Cc : public-houdini@w3.org

It seems there are a number of projects like css-layout and react-canvas who we should really be working with to help define our use cases and identify the long hanging fruit we should prioritize first.  I've added a customers list on the wiki to at least help us track these projects in one place - feel free to edit as you see fit.


On Wed, Feb 11, 2015 at 12:36 PM, Rick Byers <rbyers@chromium.org> wrote:

Absolutely.  Note that this calls out explicitly the need for performant scroll customization:

"Scrollable elements are possible in pure HTML and CSS with overflow: scroll (combined with-webkit-overflow-scrolling: touch on iOS) but these do not give you frame-by-frame control over the scrolling animation and mobile browsers have a difficult time with long, complex content."

On Wed, Feb 11, 2015 at 12:27 PM, Greg Whitworth <gwhit@microsoft.com> wrote:

Saw this today and thought it was a good example of why we should try our hardest to see Houdini to completion. It’s a good example of what a web author can do, and what they’re already doing to do their own layout and painting.




Received on Wednesday, 11 February 2015 18:09:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 February 2015 18:09:43 UTC