- From: Tobie Langel <tobie@fb.com>
- Date: Fri, 30 Nov 2012 17:04:49 +0000
- To: François REMY <francois.remy.dev@outlook.com>, "Dean Jackson" <dino@apple.com>, "Tab Atkins Jr." <jackalmage@gmail.com>
- CC: Simon Fraser <smfr@me.com>, Rik Cabanier <cabanier@gmail.com>, "www-style list" <www-style@w3.org>
On 11/30/12 5:47 PM, "François REMY" <francois.remy.dev@outlook.com> wrote: >| From: Tobie Langel >| Currently, the lack of events on which to prefetch and append new >content >| while scrolling makes it impossible to implement infinite scrolling >| without re-implementing everything in JavaScript. Other UI refinements >| (pull to refresh, etc.) suffer from similar issues. Re-implementing >| scrolling in JavaScript prevents the browsers from carrying adequate >perf >| optimization, yields sub-optimal experiences for the users and is >| extremely costly in engineering resources. > >Unfortunately, this proposal is not aimed at all at solving the 'normal' >scrolling performance, but rather at solving a popular hack around >scrolling >where you want to run 'scrolling animations' (for example a cartoon >bullet >enters the page from the left as you scroll further). Infinite scrolling requires a full re-implementation in JS of scrolling because scroll events are buffered and only triggered once the scroll is finished, which prevents new content from being pre-fetched and appended to the DOM. My understanding from reading the proposal's "Known issues" section is that Tab is looking into solutions to have animation events fired when hitting notches as "authors will want reliable, easy ways to respond to them, since the actual end of the action wonıt be easily observable (due to momentum and such)."[1] I'm not the resident expert in these matters, but it seems this would help the infinite scroll use case. Or am I understanding this completely wrong? --tobie --- [1] https://docs.google.com/document/d/1vRUo_g1il-evZs975eNzGPOuJS7H5UBxs-iZmXH ux48/edit
Received on Friday, 30 November 2012 17:05:25 UTC