Re: [csswg-drafts] [css-gcpm-3] string-set with counter(page), when is value resolved? (#4740) from Dave Cramer via GitHub on 2020-02-25 (public-css-archive@w3.org from February 2020)

From: Dave Cramer via GitHub <sysbot+gh@w3.org>
Date: Tue, 25 Feb 2020 16:13:24 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-590947393-1582647203-sysbot+gh@w3.org>

I think authors would find it tremendously confusing if the page counter did not display the value of the current page. Why should string-set freeze the value of a counter? 

> But the only way you can get "section 1" is by evaluating the _section_ counter **when the string is set**. If you evaluate it when the string is displayed, you will get the current value of the counter, which - in this example - would result in "section 3".

I don't think this is accurate. The value of the string `x` changes at several places on the page—it is "1" at the start and "3" at the end. You explicitly ask for the first value with `string-set`, so you get "1". 



-- 
GitHub Notification of comment by dauwhe
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4740#issuecomment-590947393 using your GitHub account

Received on Tuesday, 25 February 2020 16:13:26 UTC