W3C home > Mailing lists > Public > public-html@w3.org > August 2007

Re: non-leading <param>s in <object> fallback (detailed review of Semantics)

From: Ian Hickson <ian@hixie.ch>
Date: Mon, 13 Aug 2007 06:56:56 +0000 (UTC)
To: Simon Pieters <simonp@opera.com>
Cc: public-html <public-html@w3.org>
Message-ID: <Pine.LNX.4.64.0708130647490.20226@dhalsim.dreamhost.com>

On Tue, 7 Aug 2007, Simon Pieters wrote:
> 
> (This is part of my detailed review of the Semantics and structure of 
> HTML elements section.)
> 
> Step 3 in the <object> algorithm says:
> 
>   (Fallback.) The object element doesn't represent anything except what
>   the element's contents represent, ignoring any leading param element
>   children. This is the element's fallback content.
> 
> s/leading // because processing of the object takes all children 
> <param>s into account, not just the leading ones.

The rules aren't necessarily symmetric. All <param>s are taken into 
account so that the implementation can just walk through nodes filtered to 
just <param>s easily, and the fallback content is defined as all the stuff 
from the first that isn't a <param> element because that means you just 
need to walk until you find something interesting and then you just walk 
to the end without having to filter anything out.

It doesn't matter in practice because the semantics of a <param>, when it 
isn't being used for an <object>, are basically nil (iirc).

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 13 August 2007 06:57:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:03 GMT