Container -> child context enforcement

[yinonov]

enforcement of context and property value is often required where components are part of an integration within a collective.
in such cases it is advisable to enable a single source of appliance to such permutation rather than on each child element.
allowing individual value to each child within a collective can result in a "circus" like UI.
list & its list-items (as in #833), button-toggle-group, textfield and its action buttons (as explained here)
there are 2 methods to apply such enforcement

• css variables
• programmatic meddling on child components

in the recent PR on interactive icons I experienced both practices trying to consolidate 1 of the 2 practices as a rule of thumb.
BUT
thinking on each various use-cases separately leads to different choice and I feel we auto-decide on the best approach for each use-case

[lagjamhero]

I agree with handling collective elements with props and css from the top level.
Reduces repetition and chance of mistakes for the consumer

[yinonov]

see related comment