Commit 7ef14d6
committed
Fix idling? blocking on lazy iframes that Chrome never loads
Chrome fires Page.frameAttached for every iframe in the DOM, but only
fires Page.frameStoppedLoading for frames it actually loads. For a
loading="lazy" iframe parked outside the viewport (e.g. inside a closed
<details>), Chrome never starts loading it, so it never transitions to
:started_loading or :stopped_loading. It stays at state nil indefinitely.
The previous idling? required every frame to be :stopped_loading, which
meant any lazy iframe blocked idle detection for the full browser
timeout (default 5s). Treat freshly-attached frames (state nil) as idle
too — they haven't started loading, so there's nothing to wait for.
Fixes #5831 parent 25367b5 commit 7ef14d6
4 files changed
Lines changed: 27 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
| 9 | + | |
9 | 10 | | |
10 | 11 | | |
11 | 12 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
191 | 191 | | |
192 | 192 | | |
193 | 193 | | |
194 | | - | |
| 194 | + | |
195 | 195 | | |
196 | 196 | | |
197 | 197 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
125 | 125 | | |
126 | 126 | | |
127 | 127 | | |
| 128 | + | |
| 129 | + | |
| 130 | + | |
| 131 | + | |
| 132 | + | |
| 133 | + | |
| 134 | + | |
| 135 | + | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
128 | 139 | | |
129 | 140 | | |
130 | 141 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
0 commit comments