W3C home > Mailing lists > Public > www-style@w3.org > July 2010

Re: if conditions again

From: Andrew Fedoniouk <andrew.fedoniouk@live.com>
Date: Sat, 17 Jul 2010 22:35:50 -0700
Message-ID: <BAY141-DS7348743E38E9DCEF9886EF8BE0@phx.gbl>
To: "sam" <samuelp@iinet.net.au>, "Andrew Fedoniouk" <news@terrainformatica.com>
Cc: "Sebastian Hennebrueder" <usenet@laliluna.de>, "www-style list" <www-style@w3.org>

--------------------------------------------------
From: "sam" <samuelp@iinet.net.au>
Sent: Saturday, July 17, 2010 10:08 PM
To: "Andrew Fedoniouk" <news@terrainformatica.com>
Cc: "Andrew Fedoniouk" <andrew.fedoniouk@live.com>; "Sebastian Hennebrueder" 
<usenet@laliluna.de>; "www-style list" <www-style@w3.org>
Subject: Re: if conditions again

> isn't this encouraging/enabling partial implementation of CSS?

I don't really know what exactly is non-partial (a.k.a. full)
implementation of modular CSS3.

E.g. some UAs support the transition feature - some not.
Some UAs may have optional transition that is configurable
by the user. In some circumstances UAs may switch some features
in run-time, e.g. in low hardware profiles. Ideally author should
be able to create styles that are flexible in such situations.

Another particular example: gradient transitions on border-radius
are optional in CSS. How author can configure his/her style
sheets to use this feature? Without feature discoverability
declaration of such things in CSS is absolutely meaningless -
no one will rely on existence of this and so no one can use it.
I would say that feature discoverability will rather help to evolve CSS.

-- 
Andrew Fedoniouk

http://terrainformatica.com


>
> On 07/18/2010 12:18 PM, Andrew Fedoniouk wrote:
>> --------------------------------------------------
>> From: "Sebastian Hennebrueder" <usenet@laliluna.de>
>> Sent: Saturday, July 17, 2010 7:23 AM
>> To: "www-style list" <www-style@w3.org>
>> Subject: if conditions again
>>
>>> Hi all,
>>>
>>> I followed the discussion on conditions in CSS in the thread (see 2) and 
>>> were surprised that it ended suddenly.
>>>
>>> In my opinion there is a need for conditions for a number of reasons. 
>>> But I would not check for individual features but for standards and 
>>> browsers.
>>>
>>> Syntax sample inspired by Zack Weinberg (see 5)
>>> @if ( css-support <= 3){
>>> ....
>>> }
>>> @elsif (css-support = 3){
>>> ....
>>> }
>>> @else{
>>>
>>> }
>>>
>>
>> There is no need for new syntax constructions as @media (media queries) 
>> feature is already there.
>>
>> If needed we can add MQ pseudo-function like supports(feature):
>>
>> @media supports( border-radius )  { .... }
>> @media supports( transitions ) { .... }
>> @media supports( flex-units ) { .... }
>> etc.
>>
>> Each CSS3 module should define canonical "feature names" then.
>>
>
>
> 
Received on Sunday, 18 July 2010 05:36:26 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:29 GMT