..oO(KarlCore)
>I recently found something interesting with Firefox's handling of text
>within the OBJECT element.
>
>View this page on IE and the text will not be rendered to screen.
>View it in Firefox and it will.
>http://dev.karlcore.com/experimental/HTML/embed.html
>
>I've checked this with users of Safari, Opera, IE 6 and IE 7.
>
>http://www.w3.org/TR/html401/struct/objects.html#edef-OBJECT
>The W3C documentation clearly describes a sort of "if-elseif-else"
>rendering of OBJECT where the text is only supposed to display if all
>else fails with the other items before it within the parent OBJECT
>element.
>
>Please sanity check this in case it is just my version of FF that is
>b0rken.
>I am using Firefox/2.0.0.12 (the latest version)
IMHO it's not FF, but your code that causes the problem.
FF can't do much with the outer object - it doesn't have a 'type'
attribute and no 'data', but the ugly and rather Windows-specific
'classid' instead. Pretty useless. So since FF can't handle that, it
renders the content of the outer object instead, which means the inner
object and the text which follows it. Perfectly correct behaviour.
But why do you use such an ugly construct at all? The most simple
<object
type="application/x-shockwave-flash"
data="example.swf"
width="xxx" height="yyy">
<param name="movie" value="example.swf">
Alternative non-Flash content
</object>
should work in all modern browsers and even in IE 6. No need for a CC
workaround or any platform-specific attributes.
Micha
>> Stay informed about: Firefox rendering text content within OBJECT