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

Re: [CSS3] @font vs @background

From: Andrew Fedoniouk <news@terrainformatica.com>
Date: Fri, 05 Feb 2010 19:20:14 -0800
Message-ID: <4B6CDFEE.8040506@terrainformatica.com>
To: Sylvain Galineau <sylvaing@microsoft.com>
CC: www-style <www-style@w3.org>
Sylvain Galineau wrote:
>> From: www-style-request@w3.org [mailto:www-style-request@w3.org] On
>> Behalf Of Andrew Fedoniouk
>> Sent: Thursday, February 04, 2010 8:05 PM
>> To: www-style
>> Subject: [CSS3] @font vs @background
> 
> 
>> Such situation is highly non-desirable in my opinion. I tend to
>> classify
>> as a bug of language design.
> 
> But for whom is it a bug ? Is it a bug in practice i.e. are authors 
> stumbling or making errors because of it ? 
> 
> 

Could you imagine that, say, JavaScript has different precedence rules
for ',' operator inside different functions and name of the function 
will trigger different meaning for ',' operator?

Values of attributes in CSSOM are expressed as strings. So to deal with
the values you will need a parser. In current situations you cannot
create universal parser of such values that will work from now on.
I can imagine that some properties in future will use @font precedence 
rules and some @background as we are making precedent. Not exactly
very bright future for libraries like jQuery & friends.

Think about that in future we will decide that @font will need multiple
values. For example I can see good reason of having list of fonts to be 
defined this way:

font: 12pt "Times New Roman" | 10pt Arial;

Ideally lists of lists notation should not change from property to property.

-- 
Andrew Fedoniouk.

http://terrainformatica.com
Received on Saturday, 6 February 2010 03:20:33 GMT

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