You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the attachModeafterInitialTab, it appears that despite this configuration, the initial tab (indexed as 0) is rendered last in the sequence. This is particularly evident when there are multiple tabs present, where the rendering order becomes 1, 2, 0 (indexed).
This behavior has been verified across both Android and iOS platforms.
What happened?
When using the
attachMode
afterInitialTab
, it appears that despite this configuration, the initial tab (indexed as 0) is rendered last in the sequence. This is particularly evident when there are multiple tabs present, where the rendering order becomes 1, 2, 0 (indexed).This behavior has been verified across both Android and iOS platforms.
See bottomTabs relevant docs.
See original thread (private slack).
The text was updated successfully, but these errors were encountered: