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
{{ message }}
Repository navigation
Commit dca0166
Browse filesBrowse the repository at this point in the historyBrowse files
feat(browser)!: Report web vitals for bfcache restores by default (#24325)
Renames `webVitals.bfcache` to `webVitals.bfcacheNavigations` and turns
it on by default, so a back/forward-cache restore is measured like any
other page view.
Also adds e2e tests for the bfcache web vital reporting.
Copy file name to clipboardExpand all lines: MIGRATION.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -603,6 +603,20 @@ This is required for per-navigation values to be correct: `web-vitals` skips any
603
603
604
604
The visible effect is in Session Replay, which records `web-vital` breadcrumbs from the same instrumentation. Replays now contain one LCP and one CLS entry per navigation instead of one per intermediate update. Where soft navigation reporting is disabled or unsupported, the previous behaviour is unchanged.
605
605
606
+
### Back/forward-cache restores report their own web vitals
607
+
608
+
Affected SDKs: All SDKs running in the browser.
609
+
610
+
A page restored from the back/forward cache now reports its own LCP, CLS and INP, against the navigation span `browserTracingIntegration` starts for the restore and tagged `browser.navigation.type: bfcache`.
611
+
612
+
A restore is near-instant by construction, so these are a distinct population from page load vitals rather than more samples of the same thing. Read them through that attribute; pooling them with page loads will pull aggregates down. Set `webVitals: { bfcacheNavigations: false }` to leave restores unmeasured.
0 commit comments