WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
252754
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
Wednesday, February 22, 2023 5:03:30 PM UTC
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
Wednesday, February 22, 2023 5:05:56 PM UTC
Pull request:
https://github.com/WebKit/WebKit/pull/10521
EWS
Comment 2
Thursday, February 23, 2023 12:47:08 AM UTC
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
Thursday, February 23, 2023 12:48:43 AM UTC
<
rdar://problem/105806238
>
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug