Can I Do a Revealer Under Another Revealer, Or Should I Still Avoid Doing This?

[twd3]

I had some pretty bad data loss a while ago when I was doing a revealer under another revealer. Like show this stuff, then under that show this other stuff. Can I do that now? I have a request to do it but I'm afraid I'm going to see more data loss and this is a company app.

[edalzell]

how was the data lost?

[twd3]

I have no clue, I just proved it by recreating the data loss then I dumped the inside revealer and everything has been fine. So no one else has seen this? I'm pretty sure the revealer field has caused some weird stuff in the past.

[edalzell]

if you can reproduce data loss, please open an issue

[marcorieser]

From my memory: If you want the hidden fields to keep their content even when they are not visible when saving, you need to enable always_save (something like that) for those. Maybe this helps. But maybe I'm totally wrong on this one.

[twd3]

So I have to put this in place and when I get in trouble for data loss then I have to get it on video and send it to support? It won't matter anymore I'll be fired. I'll just tell this person they can't have what they want.

[edalzell]

You said above you could recreate the data loss? Sorry guess I misunderstood.

[edalzell]

You could use a toggle and conditions to mimic the revealer? We actually never use the revealer because you can't "close" it again.