W3C home > Mailing lists > Public > www-style@w3.org > January 2012

Re: [CSS21][12.2 The 'content' property] computed value on :first-line and :first-letter

From: Anton Prowse <prowse@moonhenge.net>
Date: Sun, 08 Jan 2012 21:47:21 +0100
Message-ID: <4F0A00D9.7070306@moonhenge.net>
To: www-style@w3.org
On 08/01/2012 21:38, Anton Prowse wrote:
> On 08/01/2012 21:03, Simon Sapin wrote:
>> Le 08/01/2012 20:48, Anton Prowse a écrit :
>>> On 30/11/2011 18:29, Simon Sapin wrote:
>>>> Le 30/11/2011 18:15, Simon Sapin a écrit :
>>>>> In CSS 2.1, the computed value of the 'content' property is defined
>>>>> as:
>>>>>
>>>>> """
>>>>> On elements, always computes to 'normal'. On :before and :after, if
>>>>> 'normal' is specified, computes to 'none'. Otherwise, for URI values,
>>>>> the absolute URI; for attr() values, the resulting string; for other
>>>>> keywords, as specified.
>>>>> """
>>>>
>>>> Also, replace "for other keywords, as specified" by "for other values,
>>>> as specified": values other than URIs and attr() are not all keywords,
>>>> they may be strings or counters.
>>>
>>> Simon, this is being tracked at
>>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=15458
>>>
>>> Cheers,
>>> Anton Prowse
>>> http://dev.moonhenge.net
>>>
>>
>> Great, thanks.
>>
>> I replied in Bugzilla. When an issue has an entry in Bugzilla, should
>> discussion go there, on the list, or both?
>
> On the list, please. That way we don't fragment the conversation. I
> think that the bug tracker works best for concise summaries of the
> on-list discussion.

(although in this case the fragmentation was my fault. Sorry!)

I questioned: with <string>, presumably the computed value should be the 
same as the specified value; with <counter>, should it be treated like 
attr()?

You replied:

Do you mean the computed value should be string representation of the 
counter value?

Arguably CSS 2.1 counters could be resolved to their value at "computed 
value time", but I do it later in WeasyPrint (when creating boxes from 
elements.) Not sure what other UAs do. However, css3-page introduce page 
based counters. These can definitely not have a value by the time 
computed values are required. (In paged media, we only know where page 
breaks end up when doing layout.)

I propose that both <string> and <counter> stay as specified in the 
computed value. Actually, "for other keywords" just need to become "for 
other values", which I think is what was intended.


Thanks for this useful input.

Cheers,
Anton Prowse
http://dev.moonhenge.net
Received on Sunday, 8 January 2012 20:50:18 GMT

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