WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
9201
<object> tags load frame content from render tree instead of DOM tree
https://bugs.webkit.org/show_bug.cgi?id=9201
Summary
<object> tags load frame content from render tree instead of DOM tree
Eric Seidel (no email)
Reported
2006-05-31 16:53:04 PDT
<object> tags load frame content from render tree instead of DOM tree This causes numerous problems. One of which is that object.contentDocument won't work correctly from onLoad handlers (since the load wont have been started yet. :(
Attachments
Test content which demonstrates the problem
(512 bytes, application/x-gzip)
2006-05-31 16:56 PDT
,
Eric Seidel (no email)
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Eric Seidel (no email)
Comment 1
2006-05-31 16:56:41 PDT
Created
attachment 8632
[details]
Test content which demonstrates the problem
Alexey Proskuryakov
Comment 2
2011-03-11 12:02:34 PST
Eric, what is the status of this bug? When i open the test case in Safari 5.0.4 (or in ToT), I get an alert saying "[object HTMLDocument]".
Eric Seidel (no email)
Comment 3
2011-03-11 12:05:58 PST
I moved much of the loading code out of the renderers into the DOM last summer. Obviously, this particular side effect got fixed along the way (either by my changes, or other changes, who knows?). I think we can just close this. We have a bunch of bugs with this same root cause. The most noticable being not loading display:none plugins. :)
Lucas Forschler
Comment 4
2019-02-06 09:02:58 PST
Mass moving XML DOM bugs to the "DOM" Component.
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