As per discussion on matrix in WHATWG channel; if a browser determines a page to be BFCache eligible that has not yet seen a load event fire, upon restoring the page, we effectively get a page that has seen that event be dropped entirely.
This is in non-spec'ed (or underspec'ed) territory. I will be submitting a PR for a test that tests this behavior. This issue will depend on #62559 being solved first though.
I'll file a PR that does both (solves github.com//issues/62559 and introduces test for this issue) against this issue.
As per discussion on matrix in WHATWG channel; if a browser determines a page to be BFCache eligible that has not yet seen a
loadevent fire, upon restoring the page, we effectively get a page that has seen that event be dropped entirely.This is in non-spec'ed (or underspec'ed) territory. I will be submitting a PR for a test that tests this behavior. This issue will depend on #62559 being solved first though.
I'll file a PR that does both (solves github.com//issues/62559 and introduces test for this issue) against this issue.