Bug 1882010 [wpt PR 44781] - [bfcache] Start blocking on parser abort, a=testonly
commite323de8fd56bfe898770c271a334bb78c0e3f5a7
authorrubberyuzu <yuzus@chromium.org>
Sat, 2 Mar 2024 22:40:23 +0000 (2 22:40 +0000)
committermoz-wptsync-bot <wptsync@mozilla.com>
Mon, 4 Mar 2024 09:26:42 +0000 (4 09:26 +0000)
tree50542ef3cf022464bdc07b96610f882e79bb3f5d
parentc289ed5d2227bdc70e475368a82f2f4a601c912c
Bug 1882010 [wpt PR 44781] - [bfcache] Start blocking on parser abort, a=testonly

Automatic update from web-platform-tests
[bfcache] Start blocking on parser abort

This CL adds a new NotRestoredReason when parser is aborted. This is a
sticky feature because you can't recover from cancelling the parser.

Bug: 327094393
Change-Id: I1bbce4ec707fc5c06a18e738549d0c3348a18fc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5320657
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Yuzu Saijo <yuzus@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1266269}

--

wpt-commits: 135e301b17dadf6e1e855c588688ab73af53a099
wpt-pr: 44781
testing/web-platform/tests/performance-timeline/not-restored-reasons/abort-block-bfcache.window.js
testing/web-platform/tests/performance-timeline/not-restored-reasons/test-helper.js