From c18a5349a347114e4081a525e1e5d91cd981138a Mon Sep 17 00:00:00 2001 From: Kevin Schaaf Date: Fri, 17 Nov 2017 10:08:38 -0800 Subject: [PATCH] Clarify docs on target-framerate. Fixes #4897 --- lib/elements/dom-repeat.html | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/lib/elements/dom-repeat.html b/lib/elements/dom-repeat.html index 9c0e601927..73a979ff1a 100644 --- a/lib/elements/dom-repeat.html +++ b/lib/elements/dom-repeat.html @@ -250,12 +250,16 @@ }, /** - * When `initialCount` is used, this property defines a frame rate to - * target by throttling the number of instances rendered each frame to - * not exceed the budget for the target frame rate. Setting this to a + * When `initialCount` is used, this property defines a frame rate (in + * fps) to target by throttling the number of instances rendered each + * frame to not exceed the budget for the target frame rate. The + * framerate is effectively the number of `requestAnimationFrame`s that + * it tries to allow to actually fire in a given second, and it targets + * this by empirically measuring the time between rAF's and throttling + * up/down the number of items created each `rAF`. Setting this to a * higher number will allow lower latency and higher throughput for - * things like event handlers, but will result in a longer time for the - * remaining items to complete rendering. + * event handlers and other tasks, but will result in a longer time for + * the remaining items to complete rendering. */ targetFramerate: { type: Number,