Bug 252754 - Lazily loaded frames should still get a contentWindow/contentDocument as soon as they get inserted into the document
Summary: Lazily loaded frames should still get a contentWindow/contentDocument as soon...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Chris Dumez
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2023-02-22 09:03 PST by Chris Dumez
Modified: 2023-06-21 11:52 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Dumez 2023-02-22 09:03:30 PST 
Lazily loaded frames should still get a contentWindow/contentDocument as soon as they get inserted into the document. Currently, we return null for these until the iframe moves to the viewport and gets loaded. This behavior is inconsistent with Chrome and recently caused breakage on https://www.kongregate.com (Bug 252636).
Comment 1 Chris Dumez 2023-02-22 09:05:56 PST 
Pull request: https://github.com/WebKit/WebKit/pull/10521
Comment 2 EWS 2023-02-22 16:47:08 PST 
Committed 260713@main (96e0c1e9f533): <https://commits.webkit.org/260713@main>

Reviewed commits have been landed. Closing PR #10521 and removing active labels.
Comment 3 Radar WebKit Bug Importer 2023-02-22 16:48:43 PST 
<rdar://problem/105806238>