Functionally, I think it works fine.
But there seems to be some sort of race condition going on with the action sequence that ends up creating a very confusing user experience. It’s almost like the toggle is being flipped multiple times (it isn’t) and so the screen switches between the two states 2 or 3 times before finally settling down.
I’m not exactly sure what is going on, which is why I posted that other question. It could be because some actions are being fired before a previous action is completed, or maybe it’s a data sync issue with several actions firing one after the other. But without knowing what the expected behaviour should be, that’s just wild speculation.
This is a fairly extreme example (with 70+ components on the screen, all being toggled on/off rapidly), but I’ve also observed similar behaviour with just a handful of components.