Bug 298344
| Summary: | didGeneratePageLoadTiming is called flakily when Site Isolation is disabled | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ben Nham <nham> |
| Component: | WebKit Misc. | Assignee: | Ben Nham <nham> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Ben Nham
When Site Isolation is disabled, we don't clear the frames-with-pending-subresources map when navigating to a new page. This causes the didGeneratePageLoadTiming callback to be flaky when SI is disabled, since it can cause WebPageProxy to think that the newly committed page has outstanding subresource loads, when those loads are actually associated with the previous page.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/159789224>
Ben Nham
Pull request: https://github.com/WebKit/WebKit/pull/50264
EWS
Committed 299661@main (2a61c086943c): <https://commits.webkit.org/299661@main>
Reviewed commits have been landed. Closing PR #50264 and removing active labels.