- From: Charles McCathieNevile <chaals@opera.com>
- Date: Fri, 18 Jan 2008 01:47:25 +0100
- To: "Mobile Web Best Practices Working Group WG" <public-bpwg@w3.org>
On Thu, 17 Jan 2008 23:03:18 +0100, Mobile Web Best Practices Working Group Issue Tracker <sysbot+tracker@w3.org> wrote: > ISSUE-230: OBJECTS_AND_SCRIPTS needs to address <object> with multiple > children [mobileOK Basic tests] > > http://www.w3.org/2005/MWI/BPWG/Group/track/issues/ > > Raised by: Dominique Hazaël-Massieux > On product: mobileOK Basic tests > > Dom notes that the spec assumes that <object> contains at most one > child, when that is not true. This is legal: > > <object data="foo" type="video/mpeg"> > <object data="bar" type="image/png"></object> > <object data="baz" type="image/gif"></object> > <img src="foobar" /> > Hello > </object> > > I (Sean) suggested the following rewrite to the test: > > Call an object element "usable" if and only if > - Its data attribute refers to a supported image type, OR > - It is empty (but this generates a warning), OR > - Its children are all either > - text nodes not consisting entirely of whitespace > - img elements referring to a supported image type > - "usable" object elements > > .... and then the test is merely, for each <object> (that's not a child > of an <object>), FAIL if it is not "usable" Actually, if *any* of the children refer to an accepted data type (or contain acceptable data), then this should be fine (you have to test that reference for size etc, of course). Using <object> is one way of catering for adapting content to more capable browsers... cheers Chaals -- Charles McCathieNevile Opera Software, Standards Group je parle français -- hablo español -- jeg lærer norsk http://my.opera.com/chaals Try Opera 9.5: http://snapshot.opera.com
Received on Friday, 18 January 2008 00:48:01 UTC