Help with nested objects

[David Stone]

I'm experimenting with adding fall-back objects for web pages
that might be viewed on an iPad (so no Flash!), but apparently
it isn't working so far...

Here's the page:
<http://www.chem.utoronto.ca/coursenotes/analsci/chrom/index.html>

In short, there should be two Flash player objects floated to the
right, one at each italicised subhead. The upper one uses a nested
QT movie version of the same animation as a fallback, but apparently
this doesn't show.

Either my markup is wrong, or perhaps the server is sending the
wrong http Content-Type for the movie, which would over-ride the
object type parameter? (This wouldn't altogether surprise me, but
I have no access to these settings.)

Also, are param names case-sensitive? Apple has both all-caps and
CamelCase versions in their documentation...

Here's the actual markup from the page:

<!-- Float a flash object to the right for the simple animation -->
<object class="rightside" type="application/x-shockwave-flash"
data="tlcplate.swf" height="250" width="250">
<param name="allowScriptAccess" value="sameDomain">
<param name="loop" value="false">
<param name="movie" value="tlcplate.swf">
<!-- Nest a Quicktime movie object for 'fall through' -->
<!-- Add 16 pixels to the height for controller -->
<object class="rightside" type="video/quicktime"
data="tlcplate.mov" height="266" width="250">
<param name="AutoPlay" value="false">
<param name="Controller" value="true">
<param name="PlayEveryFrame" value="true">
</object>
Some text snipped
<!-- Final fall-through is an explanatory text message -->
</object>

[tlvp]

On Tue, 08 May 2012 13:43:48 -0400, David Stone wrote:

> Also, are param names case-sensitive? Apple has both all-caps and
> CamelCase versions in their documentation...

I thought nearly everything HTML and CSS was case-sensitive, apart from the
reserved terms that go into TAG names ("A", "IMG", "TABLE", etc.) and that
serve as ATTRIBUTE names ("width", "title", "href", etc.). And, actually,
I've never actually seen any UC characters in attribute names :-) .

And nothing said above should be construed as applying to XHTML or HTML5.

HTH. Cheers, -- tlvp
--
Avant de repondre, jeter la poubelle, SVP.