Add notRestoredReasons property #20361
Conversation
github-actions
bot
added
the
data:api 🐇
Yes, I think so; I've been told this is imminent, but, converting to draft for now. |
api/PerformanceNavigationTiming.json
Outdated
| "mdn_url": "https://developer.mozilla.org/docs/Web/API/PerformanceNavigationTiming/notRestoredReasons", | ||
| "support": { | ||
| "chrome": { | ||
| "version_added": "116" |
There was a problem hiding this comment.
Turns out this did not ship in 116 after all. It's likely to be 117 but might slip to 118. Keep an eye on https://chromestatus.com/feature/5684908759449600 (which at the time of writing incorrectly states it did ship in 116).
There was a problem hiding this comment.
Thx @tunetheweb. I've updated the version to 117 for now, and will look out for other changes.
There was a problem hiding this comment.
@tunetheweb The ChromeStatus entry said it shipped in 117. Did it? ;-)
There was a problem hiding this comment.
Nope! Got them to move forward to 118 but wouldn't surprise me if that slips again. There's some discussion on the HTML standard repo PR so looking to get that all ironed out before enabling by default.
Co-authored-by: Queen Vinyl Da.i'gyu-Kazotetsu <[email protected]>
|
Chrome 119 is stable and it appears that this has still not shipped. I think that we should close this PR and wait until a) the feature is standard track, and b) there is confirmed support in a stable browser release. Note that when these two clauses are true, the mdn-bcd-collector project will let us automatically add it to BCD. |
Summary
The
PerformanceNavigationTiming.notRestoredReasonsproperty (see Back/forward cache notRestoredReasons API) is finally going to be launched in Chrome 117, or possibly 118 (See ChromeStatus page). This PR adds BCD for it.Test results and supporting details
Related issues