Adding notRestoredReasons BCD

[chrisdavidmills]

Summary

After an initial false start, Chrome 123 now supports the notRestoredReasons API. This has a bigger data footprint than before, because the notRestoredReasons return object is now properly defined as an interface, whereas it wasn't before.

Specifically, this PR includes data for:

• The PerformanceNavigationTiming.notRestoredReasons property
• The NotRestoredReasons interface
• The NotRestoredReasonDetails interface

Full disclosure — this featureset is enabled by default in Chrome 123, but it is initially being rolled out gradually to users, and ramped up to 100% provided not problems are witnessed. I wasn't sure if this should be represented somehow in the BCD, as it shouldn't be a thing for long, and it's not really partial support as such.

See https://developer.chrome.com/docs/web-platform/bfcache-notrestoredreasons for more details of this featureset.

Test results and supporting details

Related issues

[Elchi3]

Full disclosure — this featureset is enabled by default in Chrome 123, but it is initially being rolled out gradually to users, and ramped up to 100% provided not problems are witnessed. I wasn't sure if this should be represented somehow in the BCD, as it shouldn't be a thing for long, and it's not really partial support as such.

Thanks. I was wondering why I didn't detect this in my collector run for Chrome 123.
These tests look all good to me, so it seems that rollout has reached my Chrome :)

• https://mdn-bcd-collector.gooborg.com/tests/api/PerformanceNavigationTiming
• https://mdn-bcd-collector.gooborg.com/tests/api/NotRestoredReasons
• https://mdn-bcd-collector.gooborg.com/tests/api/NotRestoredReasonDetails

[queengooborg]

Hmm...this feature set seems to be another one of those feature sets that's enabled on a local version of Chrome, but not available through BrowserStack.