QuickChoice - Controlling Value Picklist Field - Literal value not accepted after edit

[honestmondayJS]

Steps to reproduce

Steps to reproduce the behavior:

1. Create a screen flow with two quick choice picklists
2. Set the 2nd picklist up as dependent picklist and add the value ({!xxx.value}) from the other picklist. On the first time it works.
3. Save flow and then try to edit the value from Controlling Value (Picklist Field) again
4. Error on field is thrown: This Flow doesn't have a defined resource with that name. If you're trying to enter a literal value, don't use {!}

Expected behaviour

The field should accept the value also on edit o

Actual behaviour

See screenshot. Value with {!xxx.value} will not be accepted anymore

Screenshots

[ericrsmith35]

Try clicking a different component on the same screen before you try and edit the QuickChoice component and see if that makes any difference.

[honestmondayJS]

Hi @ericrsmith35
I tried again with clicking away, which does not help in my case.
What I found out is a that the problem is based on the section layering I am using. If I place the quickchoice component in a section, then I only see the section as value but not the component anymore:

If I place the quickchoice components then outside, close and reopen the screen again, then the component appears as selectable:

[ericrsmith35]

@adwhite75 @alexed1 Any ideas as to why being in a section would cause this behavior? Anything we can do to QuickChoice to avoid the problem?