The dashboard that reported zero forever
A team instrumented the reporting API that tells you why a page was not restored from the back/forward cache. The dashboard has read zero blocked navigations since the day it shipped, and everyone treats that as a clean bill of health.
Six statements below describe how the instrumentation works and what the team believes about it. Three of them are why the number is zero, or why it will stay wrong. Three are correct and worth keeping.
Outside every boundary: We dropped unload for the confirm event (one blocker traded for another), Our third-party embeds (each one reports its own reasons), We stopped keeping an opener (it made both pages ineligible), How we look for a reason (reasons.includes('unload-listener')), Where we read it from (the navigation timing entry), We log restores too (the show event says it was persisted) This diagram draws no connections between its components.