[Bug]: Switching Tabs Wipes out Input Control Values

[ScottKemp]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When switching between tabs on a tab control, it will wipe out the inputted values for any controls.

Expected Behavior

I would expect any values I type into the controls to persist between tab switches.

Steps to reproduce

App is Attached

BUG_TabSwitchWipesOutInputs.json

Environment

Self Hosted 2.7.3

Additional Information

Related to #1917
???

[ScottKemp]

I also noticed similar behavior where if I had a default value for the control, switching tabs will reset to that default value, wiping out any edits I made. Probably related.

[FalkWolsky]

This is not a bug. It is a wishful behaviour. The reason is, that many users "pack" many components in individual tabs.
As they would maintain the state (like you describe as expected behaviour), the Browser and the App will get slow - cause all data is kept, even if the tab content is not visible.

We decided to add a switch to either destroy or leave the tab contents.
However, User Inputs have to be maintained by the App Creator between Tab changes.

[ScottKemp]

If you are referring to "Destroy Inactive Tab Pane", that doesn't appear to work. Even when OFF, it always resets the values.

[ScottKemp]

Here is a video describing the problem

(https://drive.google.com/file/d/1W6L8j0J1jzBDoMQEkpeVKIXvMQfxp1W0/view?usp=sharing)

[ScottKemp]

Here is a different take on the same bug. It also occurs if you have initial data in the form, change the data, switch to another tab, then switch back. Your edits then get wiped out. This is NOT what a user would expect when editing a form with multiple tabs. It really makes the tab control useless for editing record information.

Somewhere someone suggested I manually track state with every control. Now imagine every control across multiple tabs (there might be 25-100 of them for a complex record) needing to handle an on change event with an event handler, then storing the data. This is a TON of extra logic for something that should be working by default. And, combined with the problem in another bug I entered where there is a 3/4 second delay from typing verse when the event handler and {{ }} wire up occurs, they could type in to a control, quickly change tabs and unknownlingly wipe out there edits before they click save.

Retool has the correct behavior that persists any entered data in between tab changes.

I have attached another app that shows that this bug rears its head even with existing data.

BUG_TabSwitchWipesOutInputs (1).json

[ScottKemp]

Note that there is a similar bug I just entered that is similar and also preventing me from using the tab control as a UI Element. Thank you

#1949