When using tabs to organise fields inside a multi stage form, the tabs aren't hidden/shown depending on the form page. Instead, the tabs all appear at the bottom of the form. Interestingly, the tabs retain their functionality — i.e; when on the correct page, the field visibility will change when tabs are use — they just aren't hidden when on a page that doesn't have the tabs.
I took a look at the JS and the logic is really controlling visibility of elements with class .acf-field. This doesn't factor in tabs because they have a class .acf-tab-wrap.
[ ] Make sure .acf-tab-wrap is factored into the fields list
[ ] Test to see if tabs are hidden/shown on page change
[ ] Test tab functionality works as expected after the change
Did a little testing on this front and found a way but needs some further testing and refinement. Stashed locally under 'Tab support'. Will look into this for 1.10.1.
When using tabs to organise fields inside a multi stage form, the tabs aren't hidden/shown depending on the form page. Instead, the tabs all appear at the bottom of the form. Interestingly, the tabs retain their functionality — i.e; when on the correct page, the field visibility will change when tabs are use — they just aren't hidden when on a page that doesn't have the tabs.
I took a look at the JS and the logic is really controlling visibility of elements with class
.acf-field
. This doesn't factor in tabs because they have a class.acf-tab-wrap
..acf-tab-wrap
is factored into the fields list