Bug 252754

Summary:	Lazily loaded frames should still get a contentWindow/contentDocument as soon as they get inserted into the document
Product:	WebKit	Reporter:	Chris Dumez <cdumez>
Component:	WebCore Misc.	Assignee:	Chris Dumez <cdumez>
Status:	RESOLVED FIXED
Severity:	Normal	CC:	webkit-bug-importer
Priority:	P2	Keywords:	InRadar
Version:	WebKit Nightly Build
Hardware:	Unspecified
OS:	Unspecified
See Also:	https://bugs.webkit.org/show_bug.cgi?id=252636 https://bugs.webkit.org/show_bug.cgi?id=258361

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>