Bug 1793735 [wpt PR 36280] - [bfcache] Do not reset notRestoredReasons upon successfu...
commit7e8c773010e6f4afe75161b561037695d7c93320
authorBlink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Thu, 13 Oct 2022 16:11:39 +0000 (13 16:11 +0000)
committermoz-wptsync-bot <wptsync@mozilla.com>
Fri, 21 Oct 2022 10:37:54 +0000 (21 10:37 +0000)
treeab90d6078b22e595eab9a9e67c0716d0a7c65ef3
parente293bc70af59b84360e96f92e8c2b9d1ddf4febd
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
testing/web-platform/tests/html/browsers/browsing-the-web/remote-context-helper-tests/resources/test-helper.js
testing/web-platform/tests/performance-timeline/not-restored-reasons/performance-navigation-timing-bfcache-reasons-stay.window.js [new file with mode: 0644]
testing/web-platform/tests/performance-timeline/not-restored-reasons/performance-navigation-timing-bfcache.window.js
testing/web-platform/tests/performance-timeline/not-restored-reasons/performance-navigation-timing-cross-origin-bfcache.window.js
testing/web-platform/tests/performance-timeline/not-restored-reasons/performance-navigation-timing-not-bfcached.window.js
testing/web-platform/tests/performance-timeline/not-restored-reasons/performance-navigation-timing-same-origin-bfcache.window.js
testing/web-platform/tests/performance-timeline/not-restored-reasons/test-helper.js [new file with mode: 0644]