Sub Tab Whenever Shown" Actions Have Inconsistent Behaviour" | Community

Here’s a sample page to demonstrate.

Click Tab 1

Click Tab 2

Expected behaviour: Message “Sub Tab 1.2”

Actual behaviour: no message.

<skuidpage unsavedchangeswarning="yes" personalizationmode="server" showsidebar="true" useviewportmeta="true" showheader="true"> <models/> <components> <tabset rememberlastusertab="false" defertabrendering="true" uniqueid="sk-2nDz-521"> <tabs> <tab name="Tab 1"> <components> <tabset rememberlastusertab="false" defertabrendering="true" uniqueid="sk-2nDz-212"> <tabs> <tab name="Sub Tab 1.1"> <components/> <oninitialshowactions/> <onshowactions> <action type="blockUI" timeout="1500" message="Sub Tab 1.2"/> </onshowactions> </tab> <tab name="Sub Tab 1.2" loadlazypanels="true"> <components/> <oninitialshowactions/> <onshowactions> <action type="blockUI" message="Sub Tab 1.2" timeout="1500"/> </onshowactions> </tab> </tabs> <renderconditions logictype="and"/> </tabset> </components> <oninitialshowactions/> <onshowactions/> </tab> <tab name="Tab 2" loadlazypanels="true"> <components> <tabset rememberlastusertab="false" defertabrendering="true" uniqueid="sk-2nDz-717"> <tabs> <tab name="Sub Tab 2.1"> <components/> <oninitialshowactions/> <onshowactions> <action type="blockUI" message="Sub Tab 2.1" timeout="1500"/> </onshowactions> </tab> <tab name="Sub Tab 2.2" loadlazypanels="true"> <components/> <oninitialshowactions/> <onshowactions> <action type="blockUI" message="Sub Tab 2.2" timeout="1500"/> </onshowactions> </tab> </tabs> </tabset> </components> </tab> </tabs> </tabset> </components> <resources> <labels/> <javascript/> <css/> <actionsequences/> </resources> <styles> <styleitem type="background" bgtype="none"/> </styles> </skuidpage>

Page 1 / 1

Thanks for bringing this to us. This certainly appears to be an area where Skuid could improve on. I’m not exactly sure what the desired behavior here is according to the design team but whatever we choose it should be consistent behavior across the board. I’ll update you here when it has been addressed in a future release.

Reply