Bug
1793735 [wpt PR 36280] - [bfcache] Do not reset notRestoredReasons upon successful bfcache navigation, a=testonly
Automatic update from web-platform-tests
[bfcache] Do not reset notRestoredReasons upon successful bfcache navigation (#36280)
This CL makes PerformanceNavigationEntry.notRestoredReasons not reset
after successful bfcache navigation. After this CL, when the page is
successfully restored from bfcache, the reasons from the previous
navigation stay.
Now, the only time we reset the reasons is when we get a new set of
reasons.
This was discussed on the email thread here:
https://groups.google.com/a/chromium.org/g/bfcache-dev/c/fGPWPVTbyJA
Bug:
1363438
Change-Id: I5214f56e8424356cad8190c2a0144e4d1c017746
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/
3906513
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Fergal Daly <fergal@chromium.org>
Commit-Queue: Yuzu Saijo <yuzus@chromium.org>
Cr-Commit-Position: refs/heads/main@{#
1056205}
Co-authored-by: Yuzu Saijo <yuzus@chromium.org>
--
wpt-commits:
04ee132a7c7cf5f6c59b1a5819facef62f54a371
wpt-pr: 36280