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

Re: Why we need Houdini...

From: Rick Byers <rbyers@chromium.org>
Date: Wed, 11 Feb 2015 14:57:35 +1100
Message-ID: <CAFUtAY_sc=Yv_FfGNxv27AJ+YJiHizKK9JA+tbecqJDxNYQEgg@mail.gmail.com>
To: Greg Whitworth <gwhit@microsoft.com>
Cc: "public-houdini@w3.org" <public-houdini@w3.org>
It seems there are a number of projects like css-layout
<https://github.com/facebook/css-layout> and react-canvas
<https://github.com/Flipboard/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
<https://wiki.css-houdini.org/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.
>> http://engineering.flipboard.com/2015/02/mobile-web/
>> Greg
Received on Wednesday, 11 February 2015 03:58:22 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 February 2015 15:47:05 UTC