Regarding the flex grow/shrink/basis, I can confirm some weird behaviour.
When display:flex; isn’t applied, flex-grow input is not working and shrink/basis, it is required to hit the keyboard twice.
Workaround: Apply display of flex, apply the rules and then remove/disable the flex value.
I have another issue with the general mechanic.
When applying a rule or change anything else inside the flex options, display:flex; automatically gets applied.
In my opinion, this clearly shouldn’t happen.
What’s the issue here?
The design tab offers general styling options, there is no conditional show/hide of properties.
I also can see here some potential restrictions then, speaking about interactions and relative styling.
I don’t think we will be applying conditional logic for these values. While we can definitely do it, I do think this would be more of a hassle than anything in the end, just like the display:flex; property being applied automatically.
This last behaviour does need some attention. We implemented it to allow users to quickly apply flex properties without having to specifically apply flex, but I myself have found it to be irritating I specifically don’t want to apply that property, inheriting an already existing value etc…
A user preference could be perfectly suited for this.
I’m not sure to understand. Is it a user preference to activate automatic display flex when setting a value for grow/shrink/basis?
Because these specific properties have a meaning for flex direct children only, so setting grow/shrink/basis should definitely never set display flex on block.