W3C home > Mailing lists > Public > public-coremob@w3.org > October 2012

Re: Inclusion of overflowScrolling in coremob specification

From: Robert Shilston <robert.shilston@ft.com>
Date: Tue, 9 Oct 2012 20:12:21 +0100
Cc: "public-coremob@w3.org" <public-coremob@w3.org>
Message-Id: <C243B0C8-0CD4-406D-9F80-162AA0766B85@ft.com>
To: Paul Bakaus <pbakaus@zynga.com>
On 8 Oct 2012, at 10:35, Paul Bakaus wrote:
> 
>> 
>> I'm fine with tests on scroll performance. I just don't want to see useless cruft added to CSS.
> 
> 
> I am going to jump in to speak for some of the mentioned people and say that this demand, and production use case, is very real. We (Zynga) want scrolling, panning (in two directions) and zooming. We want to implement snapping, pagination between simulated pages.



I'd add that, if people have to write JS libraries (eg FTScroller [1]) to achieve things, then that ought to be considered and captured into the appropriate specs.  We've had to do just that, and are very keen for the features Zynga mention to be available from the browser rather than faking them with javascript.

[1] https://github.com/ftlabs/ftscroller

Best wishes,

Rob
-- 
Dr Robert Shilston [07940 387593 | skype:rtshilston | @rtshilston]
Director, FT Labs [labs.ft.com | 0870 085 2038 | @ftlabs]


-- 

------------------------------
This email was sent by a company owned by Pearson plc, registered office at 
80 Strand, London WC2R 0RL.  Registered in England and Wales with company 
number 53723.
Received on Tuesday, 9 October 2012 19:12:51 UTC

This archive was generated by hypermail 2.3.1 : Friday, 19 April 2013 17:36:47 UTC