- From: Arun Ranganathan <arunranga@aol.com>
- Date: Wed, 28 Mar 2007 16:57:11 -0700
- To: bzbarsky@MIT.EDU
- CC: Laurens Holst <lholst@students.cs.uu.nl>, public-html@w3.org, WHAT Working Group Mailing List <whatwg@whatwg.org>
>> Also, in reality everybody adds a two big attributes for Internet >> Explorer’s plugin finder, and an <embed> tag inside the object for >> Mozilla’s plugin finder (which still only works with <embed> and not >> <object>). > > Sorry, that's false. Plug-ins work fine with <object> in Mozilla, > _unless_ you use a "classid" attribute with a value that is an ActiveX > component ID. If you do that, Mozilla will fall back, since it > doesn't support ActiveX plug-ins. > > Now the problem is that the _only_ way IE supports plug-ins via > <object> is if they're ActiveX and the right component ID is > specified. It doesn't support dispatch based on MIME type. So you > get the nesting you mentioned. Oh, and IE does something broken if > you nest <object> inside <object>; otherwise authors could use > <object> inside <object> instead of <embed> inside <object> as they do > now. > A dated but germane discussion can be found here: http://developer.mozilla.org/en/docs/Using_the_Right_Markup_to_Invoke_Plugins -- A*
Received on Wednesday, 28 March 2007 23:57:35 UTC