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

RE: OBJECTS_OR_SCRIPTS [was mobileOK Basic 1zl - proposed LC-4 draft]

From: Jo Rabin <jrabin@mtld.mobi>
Date: Wed, 7 May 2008 16:52:07 +0100
Message-ID: <C8FFD98530207F40BD8D2CAD608B50B4F8F253@mtldsvr01.DotMobi.local>
To: "Miguel Garcia" <miguel.garcia@fundacionctic.org>, <public-bpwg@w3.org>

Miguel

This is not really right since objects can be nested to an arbitrary
depth and can contain arbitrary other elements, not only text but also
images, and so on. That's the reason the rule is stated this way. The
way we had it in the previous draft was somewhat similar to what you
propose and unfortunately though simpler, it's too simple.

Jo


> -----Original Message-----
> From: Miguel Garcia [mailto:miguel.garcia@fundacionctic.org]
> Sent: 07 May 2008 16:18
> To: Jo Rabin; public-bpwg@w3.org
> Subject: OBJECTS_OR_SCRIPTS [was mobileOK Basic 1zl - proposed LC-4
draft]
> 
> Hi,
> 
> In an multiple object nesting structure we must ensure a suitable
> content is provided to the user. This content will be browser
dependant
> (it will depend on which mime types are supported by the browser). We
> don't mind (at least at mobileOK Basic level) if the content provided
is
> the best that fits device capabilities. Our only concern is that at
the
> end of the object chain (the worst case, none of the nested objects
are
> supported) there is a text alternative.
> 
> With these assumptions in mind the object checking of
OBJECTS_OR_SCRIPTS
> may be as simple as:
> 
> --- begin proposed text ---
> For each object element that has no object element ancestor:
> 	If the TEXT content of the object element and all nested objects
> is empty, warn
> 
> 	If the TEXT content of the object element and all nested objects
> consists only of white space, FAIL
> --- end proposed text ---
> 
> Miguel
Received on Wednesday, 7 May 2008 15:52:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:42:58 UTC