I see your created post has the issue, not my posts.
I followed the precise same steps.
I repeated those precise steps today on that same duplicate you sent back. Of course, it doesn't work this time 🙂
I tried the same steps from here, https://toolset.com/forums/topic/problem-with-multiple-hidden-container-blocks/#post-1536639, and guess what - I also failed.
I would like to emphasize that just yesterday I sent you a working copy, where the precise steps where followed not on one, but two pages, all working fine 🙂
Better even, after a few trials on the duplicate, I was again able to make it work.
I then deleted (from a saved page) the containers.
I re-added them, they work now 😀
I thought, maybe the sequence with which we save the settings influences the code, and hence threw the two blocks Codes in a Diff checker, and I found a difference.
Indeed, while in the broken version the rules for phone come after the rules of tablet in the code, on the working version that's inverted.
As soon as both containers have the same order of phone/tablet rules in the code, then it works
If they are inverted, the first container fails.
That order is determined by how we actually save the settings for visibility, I confirmed this:
if you are to first hide a container on mobile, then on the tablet, that's the sequence it'll save in the code.
As long all>/em> your hide elements follow that same sequence of first hiding phone and then only tablet it'll work fine, as soon you once save first the table settings it'll break
Of course, I then tried to verify these observed symptoms on a fresh page and , of course, 😀 it won't be an issue at all, it'll just work fine no matter what order the code has.
It remains a mystery to me how this happens but it is related to the sequence with which we save the settings of the visibility.
I'll send the duplicate to the developers, thanks for pointing this (very weird) issue out to us.