-
Rakina Zata Amni authored
This CL make us check for blocklisted features in CanStoreRenderFrameHostLater, which is called when determining whether we should do a proactive BrowsingInstance swap or not. We don't currently have support for knowing that a blocklisted API is no longer used after pagehide. This means if a blocklisted feature before navigation, it will always be ineligible for bfcache. We should not try to do a BrowsingInstance swap, etc. in this case. In the future, as we add support for blocklisted APIs to be deemed as no longer used after it was torn down in pagehide, we can move the check for the newly supported APIs one by one to CanStoreRenderFrameHostNow. More context: https://groups.google.com/a/google.com/g/chrome-bfcache/c/L-ZreZDY4n0/m/8cBbBGB5CQAJ Bug: 1129331 Change-Id: Ic1756d8c8460036dc97603b38b4251fb7894f9fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2442397 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Yuzu Saijo <yuzus@chromium.org> Cr-Commit-Position: refs/heads/master@{#813505}
9fd73cca