W3C home > Mailing lists > Public > www-html@w3.org > June 2005

Re: [XHTML 2] 24.1 OBJECT declare and "completed loading" (PR#7751)

From: Sebastian Redl <sebastian.redl@getdesigned.at>
Date: Wed, 01 Jun 2005 11:29:31 +0200
Message-ID: <429D7FFB.1000606@getdesigned.at>
To: www-html@w3.org

Justin Wood (Callek) wrote:

> Regarding the last one, how would you be able to "define" this;
>
> [....]
> <a href="#notAvalidFragment">foo</a>
> <a href="#object1">Activate Some Object Defined Later in Document</a>
> <object id="object1" declare="declare" ... a video ... />
> <object id="object2" declare="declare" ... a second video ... />
> <a href="#object2">Activate Some Object Defined Earlier in Document</a>
> [....]
>
> The Object 2 link seems the only one which could be "reliably"
> disabled *as the document loads*, sure depending on relative placement
> of the Object 1 link, and Object 1 itself, it may be possible to
> assign the disabled flag to Object 1's link as well, but is
> near-futile;  The links will still be _there_ though they do not
> necessarily have to target any real fragment.  [Though a real fragment
> is good practice]
>
> ~Justin Wood (Callek)
>
This snippet is invalid. 24.2.2 says:
> A declared object
<http://www.w3.org/TR/2005/WD-xhtml2-20050527/mod-object.html#edef_object_object>
element must appear in a document before the first time the object data
is referenced. For example, the
> declaring object element must appear before a link referencing the
object data.

Thus, the behaviour of the first two links is undefined.

Sebastian Redl
Received on Wednesday, 1 June 2005 09:29:29 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:19:03 UTC