You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,6 +71,8 @@ const Component = () => {
71
71
};
72
72
```
73
73
74
+
> **Note:** The first `false` notification from the underlying IntersectionObserver is ignored so your handlers only run after a real visibility change. Subsequent transitions still report both `true` and `false` states as the element enters and leaves the viewport.
75
+
74
76
### `useOnInView` hook
75
77
76
78
```js
@@ -103,6 +105,8 @@ Key differences from `useInView`:
103
105
-**Similar options** - Accepts all the same [options](#options) as `useInView`
104
106
except `onChange`, `initialInView`, and `fallbackInView`
105
107
108
+
> **Note:** Just like `useInView`, the initial `false` notification is skipped. Your callback fires the first time the element becomes visible (and on every subsequent enter/leave transition).
> **Note:**`<InView>` mirrors the hook behaviour—it suppresses the very first `false` notification so render props and `onChange` handlers only run after a genuine visibility change.
0 commit comments