RESOLVED FIXED252754
Lazily loaded frames should still get a contentWindow/contentDocument as soon as they get inserted into the document 
https://bugs.webkit.org/show_bug.cgi?id=252754
Summary Lazily loaded frames should still get a contentWindow/contentDocument as soon...
Chris Dumez
Reported 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).
Attachments
Add attachment proposed patch, testcase, etc.
Chris Dumez
Comment 1 2023-02-22 09:05:56 PST
Pull request: https://github.com/WebKit/WebKit/pull/10521
EWS
Comment 2 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.
Radar WebKit Bug Importer
Comment 3 2023-02-22 16:48:43 PST
<rdar://problem/105806238>
Note You need to log in before you can comment on or make changes to this bug.