Re: ISSUE-41: extensibility change proposal advocates

Paul Cotton, Wed, 4 Aug 2010 17:20:11 +0000:

> Before the Chairs issue a survey on this issue we would like to 
> ensure that there is AT LEAST one "advocate" in the WG for each of 
> the five change proposals.  

> 2. Change Proposal: "Proposal Y", Hyphen-Separated Vendor-Prefixed 
> Attributes 
> http://www.w3.org/html/wg/wiki/ChangeProposals/fixedprefixsimple  

Could some of the vendors that actually, eventually "advocates" vendor 
prefixes help me understand how, in reality, you would make use of 
those prefixes? Thinking in analogy to CSS. I see two solutions, 
myself, but I don't know what you are after. Let us imagine that Webkit 
wants to announce and/or enable that it has experimental support for a 
new element. It could then one of two things:

1) 

<SuperNewElement" 
 _webkit:supported="ON" src"movie"
 xmlns:_webkit="http://www.webkit.org" ></SuperNewElement>

2)

<SuperNewElement" _webkit="_webkit" src"movie" ></SuperNewElement>

In the first example, the very namespace is under Webkit's control - it 
decides what the namespace should be. In HTML it should work without 
namespaces declaration. (While in HTML, the namespace declaration is 
snot needed]. 

In the latter example, Webkit has been allowed a single boolean, 
attribute, in the HTML namespaec, and whose semantics is predefined: it 
expresses that Webkit only supports this element whenever the _webkit 
boolean attribute is present. (I try to think in analogy to CSS.)  

If it is the latter example you are after, then namespace for this 
seems like overkill. It even seems like an overkill to have boolean 
attribute. Something like this seems better:

<SuperNewElement" partly-supported-status="webkit mozilla" src"movie" 
></SuperNewElement>

However, I am not sure that browser vendor prefixes is such an good 
idea. Are there any example use cases for when it would be useful?
-- 
leif halvard silli

Received on Thursday, 5 August 2010 04:00:56 UTC