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

"Justin Wood (Callek)" <116057@bacon.qcc.mass.edu>
>> Add an attribute to the OBJECT such that the author can suggest if it can 
>> be activated before the document is loaded, and add a conformance 
>> requirement that the UA style any links to ones that can't be in a 
>> disabled state until the onload event fires.
>>
> 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]

href="#" references must come after their <object declare definitions, so 
the 2nd link is not an issue we need to concern ourself, see
24.2.2. [...]
| A declared 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.

I would like to see internal references to #'s that aren't defined also be 
non-conformant, to remove any issues with the first example link above.

Cheers,

Jim.

Received on Tuesday, 31 May 2005 20:56:03 UTC