Open dbaron opened 2 years ago
It is notable that this list does not include the scope. Does this imply that if the scope in a specifier changes, you end up with two toggles with the same name on the same element, with different scopes? Or should it list scope as well?
It definitely shouldn't make another one. It probably should list scope, I'll have to look closely at this.
Also, this statement seems to contradict 2. Toggle Concepts, which says:
It's not contradictory - the values aren't changed, they can just be overridden at time-of-use. But it's definitely phrased somewhat confusingly. ^_^
Oh, I realized that if scope should override, that overriding should be in the fire a toggle activation algorithm.
(Though I think making scope override would make things a good bit harder; it's probably easier as-is.)
3. Creating a Toggle: the toggle-root property says:
It is notable that this list does not include the scope. Does this imply that if the scope in a specifier changes, you end up with two toggles with the same name on the same element, with different scopes? Or should it list scope as well?
Also, this statement seems to contradict 2. Toggle Concepts, which says: