how does repeating the same name for toggle-root and toggle-group work?

[dbaron]

There are a number of aspects of the specification that are poorly defined if toggle-root or toggle-group use the same toggle name more than once in their list of toggles. I think these things either need to be defined more clearly, or forbidden.

For example:

• which toggle specifier takes precedence when originally creating the toggle for the element?
• which "override specifier" is used in the "change a toggle" algorithm?
• when multiple toggle groups are listed, in which order are they processed? Is it possible for an element to create more than one active toggle group scope (one with narrow scope, one with wide scope containing only the elements not in narrow scope) and which order of specifying groups achieves this?

[tabatkins]

I definitely need to define a precedence, but don't have a strong preference either way. I think it's most consistent with other CSS to say that last wins, as this is how cascade works, and more directly analogous, this is how animations work. (Effectively; when multiple animations affect the same property the last one in 'animation-name' order wins, so animation-name: foo, bar, foo; is effectively identical to animation-name: bar, foo;. There might be two foo animations observable via the scripting API, I dunno.)