W3C home > Mailing lists > Public > public-bpwg@w3.org > January 2008

Re: ISSUE-230: OBJECTS_AND_SCRIPTS needs to address <object> with multiple children [mobileOK Basic tests]

From: Sean Owen <srowen@google.com>
Date: Fri, 18 Jan 2008 00:41:54 -0500
Message-ID: <e920a71c0801172141h5e14e6d1y4fd3efb318f97417@mail.gmail.com>
To: "Charles McCathieNevile" <chaals@opera.com>
Cc: "Mobile Web Best Practices Working Group WG" <public-bpwg@w3.org>
I don't mind taking that view, but, it seems that when the body of an
<object> tag, which is the fallback that is rendered when the <object>
can't be, is at least partially not supported, this should not be
considered OK any more than if the body of the <object> was a single
other <object> that can't be rendered.

On Jan 17, 2008 7:47 PM, Charles McCathieNevile <chaals@opera.com> wrote:
>
>
> 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 05:42:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:51 UTC