Bug 86682 - <embed> and <object> width and height do not interact properly
Summary: <embed> and <object> width and height do not interact properly
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Robert Hogan
URL: http://code.google.com/p/chromium/iss...
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-16 15:14 PDT by Robert Hogan
Modified: 2012-05-29 12:03 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Hogan 2012-05-16 15:14:31 PDT 
Reduction:

   <OBJECT classid>
   <PARAM NAME=movie VALUE="eat.swf"> <PARAM NAME=menu VALUE=false> <PARAM  NAME=quality VALUE=high> <PARAM NAME=bgcolor VALUE=#231f1c> <EMBED src="eat.swf" menu=false quality=high bgcolor=#231f1c  WIDTH="100" HEIGHT="180" NAME="eat" ALIGN=""
 TYPE="application/x-shockwave-flash" PLUGINSPAGE="http://www.macromedia.com/go/getflashplayer"></EMBED>
    </OBJECT>
​
See also https://bugs.webkit.org/show_bug.cgi?id=17688#add_comment
Comment 2 Robert Hogan 2012-05-16 15:39:15 PDT 
The culprit seems to be:

<object><PARAM NAME=movie VALUE="eat.swf">

Specifying a source for the object element results in the dimensions for the embedded object getting ignored.
Comment 3 Robert Hogan 2012-05-20 11:51:21 PDT 
If you try this reduction you can see different results for Opera/FF/IE8 vs WebKit: http://jsfiddle.net/yZ6zV/

HTMLObjectElement::parametersForPlugin() special-cases 'movie' as a PARAM NAME and attempts to load the value passed to it - it looks like no other browser does this. It's done for 'compatibility' - presumably with WebKit-apps rather than other browsers.

Adobe says that flash requires a width and height parameter in the OBJECT element and these are missing in the site reporting the issue (http://helpx.adobe.com/flash/kb/flash-object-embed-tag-attributes.html).

So this looks like a combination of WebKit-specific behaviour and invalid code from the reporter.

Is the bug invalid?