Re: [csswg-drafts] [css-gcpm-3] string-set with counter(page), when is value resolved? (#4740)

First, you can always display the page counter in the margin content with `content: counter(page)`.  That's unambiguous.

Absolutely, string `x` is "1" at the start and "3" at the end. That's entirely my point! It means that every time you set the value of "x", you assign it _a snapshot of the current value of the counter_. The String "x" is assigned three different values on the page, and when I display it in the margin with `string()` I choose which of these assignments I want to display - first, last etc.

If "x" were instead set to simply _point to the latest value of the "section" counter_, instead of taking a snapshot of the value, then the value displayed in the margins would always be the most recent value of the counter. This is not at all what we want in this case.

But that's exactly what's happening if we set it to the "page" counter.

Does that make a bit more sense?



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

Received on Tuesday, 25 February 2020 17:00:28 UTC