NotRestoredReasons API has been launched as part of PerformanceNavigationTiming API. This PR specified the names of the reasons that User Agents can choose to expose. https://github.com/whatwg/html/pull/10154 This entry is about chromium changing the names of the reasons so that they match the ones specified. List of changes: "extension-messaging", "pending-permission-request", "not-main-frame", "frame-navigating", "timeout", "cookie-disabled", "cookie-removed", "printing", "web-database", "injected-javascript", "injected-stylesheet" -> "masked" "response-method-not-get"->"request-method-not-get" "serviceworker-version-activation" -> "serviceworker-version-activated" "serviceworker-added-after-bfcache" -> "serviceworker-added" "serviceworker-unregistration" -> "serviceworker-unregistered" "unload-handler" -> "unload-listener" "session-restored" -> null
We are going to change the names reported in NotRestoredReasons API so that they match the specified names. NotRestoredReasons API has been launched for 6 months now. The change is likely to land with a flag in M133. We expect that web developers are counting these values. Since this is an API that reports events about a previous instance of the page, we do not expect that any client-side code takes any action based on specific strings. Server side code which presents reports based on this API's data may attach advice to developers on how to avoid blocking BFCache for certain reasons. This would need to attach the advice to the new values and the old values. Similarly developer-targeted articles may reference the old values.