W3C home > Mailing lists > Public > public-html@w3.org > January 2010

Re: ISSUE-95 hidden - Chairs Solicit Proposals

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Fri, 29 Jan 2010 19:26:18 +0100
To: Krzysztof Maczyński <1981km@gmail.com>
Cc: public-html@w3.org, Jonas Sicking <jonas@sicking.cc>
Message-ID: <20100129192618563217.6bede11a@xn--mlform-iua.no>
Jonas Sicking, Fri, 29 Jan 2010 10:00:16 -0800:

>> @stored (or similar) sounds like the name you are looking for.

> Aren't all nodes "stored" in the DOM? The difference with these nodes
> being that they are *just* stored, not visually or semantically
> visual.

Does that make it an unclear name, you mean? In case of yes, then I 
disagree. The reason why @declare (for <object>) has been obsoleted has 
nothing to with the name.  

Krzysztof Maczyński, Fri, 29 Jan 2010 18:26:26 +0100:
>> ]]
>> This attribute specifies a message that a user agent may render while 
>> loading the object's implementation and data.
>> [[

> My mistake, I meant declare.

@declare is close!  And I agree that it could be useful to redefine 
@declare instead of inventing a new attribute. 

How would you define @declare to ensure that it did not become 
incompatible with "the Web"/HTML4? Are there any plug-ins/UAs/scripts 
that react to <object declare>? 

This is what HTML4 says about @declare:

]]
When present, this boolean attribute makes the current OBJECT 
definition a declaration only. The object must be instantiated by a 
subsequent OBJECT definition referring to this declaration.
[[
-- 
leif halvard silli
Received on Friday, 29 January 2010 18:26:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:00 GMT