- From: Brad Kemper <brad.kemper@gmail.com>
- Date: Tue, 23 Dec 2014 21:57:32 -0800
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: John Fischer <jfroffice@gmail.com>, Benjamin Poulain <benjamin@webkit.org>, www-style list <www-style@w3.org>
> On Dec 22, 2014, at 11:21 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > > Anything with a "smaller" loop, particularly one that takes place > solely in layout code, is much more difficult to deal with. You don't > have a natural place to break loops, and layout doesn't have the > ability to complete a full cycle with stable information, because it > depends on its own computations. You could just check when items are added or removed from the DOM and when scrolling stops for more than a 1/10 second or whatever, and break the loop after that until after the next sustained scroll event.
Received on Wednesday, 24 December 2014 05:58:01 UTC