W3C home > Mailing lists > Public > public-appformats@w3.org > October 2006

Re: [XBL] CSS support for XBL 2.0 user agents: Yes or no?

From: Karl Dubost <karl@w3.org>
Date: Fri, 6 Oct 2006 12:17:34 +0900
Message-Id: <A3AC542E-79BA-4E48-9C83-C0FA345C73F0@w3.org>
Cc: public-appformats@w3.org
To: Ian Hickson <ian@hixie.ch>


Le 6 oct. 06 à 10:20, Ian Hickson a écrit :
> On Thu, 5 Oct 2006 karl@w3.org wrote:
>>
>> # XBL user agents that do not support CSS should not render the XBL
>> # elements.
>>
>> Though earlier in the specification, it is said:
>>
>> # The element attribute of the binding element and the includes  
>> attribute
>> # of the content element, if specified, must be parsed according  
>> to the
>> # rules in the Selectors specification. [SELECTORS]
>
> I do not understand the reference to the part of the specification  
> that
> mentions Selectors above. What about it?

In http://www.w3.org/TR/2006/WD-xbl-20060907/#attributes
	The element attribute of the binding element and the includes
	attribute of the content element, if specified, must be parsed
	according to the rules in the Selectors specification. [SELECTORS]

User Agents have to implement CSS 3 Selectors to parse the value of  
"element" attribute and the value of "includes" attribute.

>> The XBL 2 specification has to define what "do not support CSS"  
>> means.
>> Which level, and/or which individual modules?
>
> It doesn't really matter -- the specification gives two options,  
> one for
> CSS-aware UAs, and one for CSS-unaware UAs. Whether or not a  
> particular UA
> supports CSS or not is up to the UA's vendor, really; the result  
> either
> way as far as XBL is concerned is the same. Basically this is just
> requiring a behaviour and then describing it in terms of CSS, so  
> that it
> can be overridden in CSS contexts.
>
> Let me know if this doesn't satisfy you.

A user agent which is "not CSS-aware" and then might not implement  
CSS 3 Selectors will not be able to process the values of the  
attributes. The two requirements seems to be conflicting.  Maybe a  
text like

	XBL user agents that do not support CSS Rendering modules
	should not render the XBL elements other than the div
	element, which they should render as a paragraph-like
	element.

would be clearer.  It is not clear what means "supporting CSS"  
without reference to specifications, modules, profiles or level. The  
CSS specifications mentionned in the document are

	- CSS3 Basic User Interface Module
	- Media Queries
	- Selectors

Is it a kind of "XBL CSS Profile" which would be enough to define  
"supporting CSS" or is there more?


Does it clarify the comment?




-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***
Received on Friday, 6 October 2006 03:17:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:50:05 UTC