Bug 66870
| Summary: | Don't create plugin document for <embed> element inside HTML. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Yongjun Zhang <yongjun_zhang> |
| Component: | Plug-ins | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | abarth, aestes, ap, eric.carlson, eric, sam |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac | ||
| OS: | Unspecified | ||
Yongjun Zhang
In WebKit nightly, a intermedia plugin document will be created for the following HTML:
<html><body>
<embed src="http://www.tumblr.com/video_file/7780794748/tumblr_lok02dYCYQ1qbygpz">
</body></html>
and the DOM is changed to:
<embed>
<html>
<body>
<video>...
</body>
</html>
</embed>
We should not create the plugin document if the embed element is already inside a body.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Yongjun Zhang
<rdar://problem/10015932>
Eric Seidel (no email)
I'm confused. This is a performance issue?
Andy Estes
There are a few problems here as I see it:
1) It is incorrect per the spec to allow <embed> resources to load as subframes. Only <object> elements should be allowed to load as a subframe.
2) We don't handle well the case where we don't know if an <embed> or <object> resource should load in a plug-in up front. Currently we handle this case by going down the subframe loading path, then creating a plug-in document once we get a MIME type from the response. It'd be better if we just created the plug-in at this point instead of doing the plugin-inside-iframe thing we currently do.
So I think there are really two bugs here.
Alexey Proskuryakov
Mass closing plug-in bugs, as plug-in support has been removed from WebKit.
Please comment and/or reopen if this still affects WebKit in some way.