Can we access your project?
Current Behavior
Subject: Possible bug with Set Form Field on widgets inside a conditionally hidden Container
I found a possible bug related to the Set Form Field action and Conditional Visibility.
I have a page/component with several rows. Each row starts with a Container containing multiple form fields.
One of these Containers was created only for documentation/reference purposes and was set to invisible using Conditional Visibility. Inside this hidden Container, there were two form fields that were not actually needed by the user.
During the page/component initialization, I use a sequence of Set Form Field actions to populate the fields with data from a database record.
The problem was that the action flow was unexpectedly interrupted. Using Alert Dialog actions for debugging, I was able to identify exactly where the execution stopped.
The flow consistently stopped when FlutterFlow executed Set Form Field for a field located inside the conditionally invisible Container. Actions placed after that point were not executed.
After I disabled/removed the Set Form Field action targeting that hidden field, the entire action flow started working normally again.
Expected Behavior
Steps to reproduce:
Create a Container containing a TextField.
Make the Container invisible using Conditional Visibility.
During page/component initialization, execute Set Form Field targeting the TextField inside that hidden Container.
Add another action immediately afterward, such as an Alert Dialog.
In my case, execution stops at the Set Form Field action and the subsequent actions are never executed.
There was no obvious error indicating that the hidden field was responsible, which made the issue particularly difficult to diagnose.
It appears that Set Form Field may interrupt the Action Flow when its target widget is inside a Container that is not currently rendered due to Conditional Visibility.
Steps to Reproduce
Steps to reproduce:
Create a Container containing a TextField.
Make the Container invisible using Conditional Visibility.
During page/component initialization, execute Set Form Field targeting the TextField inside that hidden Container.
Add another action immediately afterward, such as an Alert Dialog.
In my case, execution stops at the Set Form Field action and the subsequent actions are never executed.
There was no obvious error indicating that the hidden field was responsible, which made the issue particularly difficult to diagnose.
It appears that Set Form Field may interrupt the Action Flow when its target widget is inside a Container that is not currently rendered due to Conditional Visibility.
Reproducible from Blank
Bug Report Code (Required)
IT40l/GA34p2schE1qqBcMJVtDw5JW42UOc41up7aCsofePrOpkAf8/7UFtUOeKqSlVLfGf9q3IX/Mr5iePTNfUVHyWtGKZ6/pYMFgyUXXOibJiDPa63b3BPJ/5UFWKD4J6N3yJ5OvN0S1Yc1GGAIdzITgzcQ4T6Im4jPea4XdeK2SrDX1iXc2URm05KZDPz
Visual documentation
...
Environment
- FlutterFlow version: 7.0.73
- Platform:
- Browser name and version: google
- Operating system and version affected: windows
Additional Information
No response
Can we access your project?
Current Behavior
Subject: Possible bug with Set Form Field on widgets inside a conditionally hidden Container
I found a possible bug related to the Set Form Field action and Conditional Visibility.
I have a page/component with several rows. Each row starts with a Container containing multiple form fields.
One of these Containers was created only for documentation/reference purposes and was set to invisible using Conditional Visibility. Inside this hidden Container, there were two form fields that were not actually needed by the user.
During the page/component initialization, I use a sequence of Set Form Field actions to populate the fields with data from a database record.
The problem was that the action flow was unexpectedly interrupted. Using Alert Dialog actions for debugging, I was able to identify exactly where the execution stopped.
The flow consistently stopped when FlutterFlow executed Set Form Field for a field located inside the conditionally invisible Container. Actions placed after that point were not executed.
After I disabled/removed the Set Form Field action targeting that hidden field, the entire action flow started working normally again.
Expected Behavior
Steps to reproduce:
Create a Container containing a TextField.
Make the Container invisible using Conditional Visibility.
During page/component initialization, execute Set Form Field targeting the TextField inside that hidden Container.
Add another action immediately afterward, such as an Alert Dialog.
In my case, execution stops at the Set Form Field action and the subsequent actions are never executed.
There was no obvious error indicating that the hidden field was responsible, which made the issue particularly difficult to diagnose.
It appears that Set Form Field may interrupt the Action Flow when its target widget is inside a Container that is not currently rendered due to Conditional Visibility.
Steps to Reproduce
Steps to reproduce:
Create a Container containing a TextField.
Make the Container invisible using Conditional Visibility.
During page/component initialization, execute Set Form Field targeting the TextField inside that hidden Container.
Add another action immediately afterward, such as an Alert Dialog.
In my case, execution stops at the Set Form Field action and the subsequent actions are never executed.
There was no obvious error indicating that the hidden field was responsible, which made the issue particularly difficult to diagnose.
It appears that Set Form Field may interrupt the Action Flow when its target widget is inside a Container that is not currently rendered due to Conditional Visibility.
Reproducible from Blank
Bug Report Code (Required)
IT40l/GA34p2schE1qqBcMJVtDw5JW42UOc41up7aCsofePrOpkAf8/7UFtUOeKqSlVLfGf9q3IX/Mr5iePTNfUVHyWtGKZ6/pYMFgyUXXOibJiDPa63b3BPJ/5UFWKD4J6N3yJ5OvN0S1Yc1GGAIdzITgzcQ4T6Im4jPea4XdeK2SrDX1iXc2URm05KZDPz
Visual documentation
...
Environment
Additional Information
No response