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: Wed, 11 Jan 2012 22:05:30 +0100
Message-ID: <4F0DF99A.3050108@moonhenge.net>
To: www-style@w3.org
(Just for the record, it wasn't me who wrote that but Simon Sapin; I was 
quoting him!)

Thanks for the info, Tab.


On 11/01/2012 20:30, Tab Atkins Jr. wrote:
> On Sun, Jan 8, 2012 at 12:47 PM, Anton Prowse<prowse@moonhenge.net>  wrote:
>> 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.
>
> 2.1 doesn't actually specify one way or another whether counters are
> kept as-is or turned into the string they represent at computed-value
> time.  However, all browsers agree that they're kept as-is.  Lists
> matches this in its definition of the computed value of 'content' on
> ::marker.
Received on Wednesday, 11 January 2012 21:06:19 GMT

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