[css-contain] Do scoped counters create new counters?

[Loirooriol]

From Style Containment,

For example, if counter-increment is scoped to an element, the first use of it within the subtree acts as if the named counter were set to 0 at the scoping element, regardless of whether the counter had been used outside the scoping element. Any increments made within the subtree have no effect on counters of the same name outside the scoping element.

But it's not much clear if a scoped counter-increment creates a new counter or not.

That is, what is the expected output of

<div></div>

div {
  contain: style;
  counter-increment: n;
}
div::before {
  counter-increment: n 2;
  content: counters(n, '.');
}

Is it 1.2 or just 2?

[Loirooriol]

OK, since content is scoped, I think the output is just 2.

But note that CSS Lists will allow counters() anywhere that accepts a <string>, so what about background: url( counters(n, '.') )? Is the background image retrieved from 1.2 or just 2?

Maybe you should scope counters() itself.

[css-meeting-bot]

The Working Group just discussed Scoped Counters, and agreed to the following resolutions:

• RESOLVED: create new counter scopes at style scoping root for style containment

The full IRC log of that discussion

<fantasai> Topic: Scoped Counters
<astearns> github: https://github.com//issues/1887
<fantasai> TabAtkins: If you have a style scoped element, which says counters are scoped to the subtree
<fantasai> TabAtkins: does that create a new counter?
<fantasai> s/that/counter-increment/
<fremy> +1 on this one
<fantasai> TabAtkins: or does it increment the existing counter from the outside
<fantasai> TabAtkins: I think it should implicitly create a new counter scope at the style scoping root
<fantasai> fantasai: And so counters() would reveal a new level of counter?
<fantasai> TabAtkins: yes
<fantasai> TabAtkins: Don't want to fuss with the subtree when calculating counters further down in the document
<fantasai> fantasai: so you're disagreeing with Oriol's comment?
<fantasai> TabAtkins: ...
<fantasai> astearns: Write a test?
<TabAtkins> s/.../yes/
<fantasai> astearns: So proposed to implicitly create new counter scopes at style scoping root for style containment
<fantasai> RESOLVED: create new counter scopes at style scoping root for style containment

[frivoal]

@Loirooriol The resolution agrees with you that it needs to be defined, but defines it differently from what you suggested. Please confirm that this outcome is acceptable to you.

[Loirooriol]

The behavior is acceptable, but I think the spec is a bit confusing because it says that content is scoped, i.e

must act as if the scoping element was the root of the document for the purpose of evaluating the property’s effects

but then content can read counter values from ancestors. So it doesn't really act as the root.

[frivoal]

I guess the problem is that it says that content is scoped (for the purpose of open-quote/etc values) and that the etc doesn't make it totally clear what is concerned and what is not.

[frivoal]

@Loirooriol I opened #2483 to follow up on this.

[Loirooriol]

Yes, that's the problem.

BTW, Chrome outputs 2 instead of 1.2. Somebody should tell them.