As a way to discourage developers from enabling occlusion detection -- which is likely to be expensive to compute and may negatively affect page performance -- unless they really need it, maybe we should also add a throttleFrequency flag to IntersectionObserverInit, with the following behavior:
throttleFrequency: if true, then observations are computed no more frequently than once per 100ms.
trackVisibility: if true, and if throttleFrequency is true, then compute and report occlusion detection. If throttleFrequency is false, then this option is ignored.
As a way to discourage developers from enabling occlusion detection -- which is likely to be expensive to compute and may negatively affect page performance -- unless they really need it, maybe we should also add a throttleFrequency flag to IntersectionObserverInit, with the following behavior:
throttleFrequency: if true, then observations are computed no more frequently than once per 100ms.
trackVisibility: if true, and if throttleFrequency is true, then compute and report occlusion detection. If throttleFrequency is false, then this option is ignored.