Tab Layout


This article describes functionality and guidance that is in public preview and may be substantially modified before it's generally available. Microsoft makes no warranties, express or implied, with respect to the information provided here.

The TabLayout is a customized TabLayout. When the application is spanned across displays on a device with a vertical folding feature, the displayPosition parameter can be used to make the widget render on the left, right or above the folding feature.


Returns or sets a value that specifies on which screen the view will render. Can be one of the three values:

  • DisplayPosition.START
  • DisplayPosition.END
  • DisplayPosition.DUAL

These are explained in detail below.


Tabs are grouped on the first screen. START: tabs on the first screen


Tabs are grouped on the second screen. END: tabs on the first screen


Tabs are spanned across both screens. Tabs may appear under the folding feature, and this is generally undesirable behavior. Use arrangeButtons to avoid this. DUAL: tabs on both

tabLayout.displayPosition = DisplayPosition.START

The same can be obtained using the app:display_position attribute:



When the application is spanned over the folding feature and the component has an odd number of buttons, the middle one could be obstructed by the hinge or fold. One way to avoid this is to arrange the buttons differently on each side of the folding feature:

The buttons can be arranged in different ways on the two screens

This can be accomplished with the arrangeButtons function.

tabLayout.arrangeButtons(2, 4)


When the application is spanned and there are no buttons on a screen, the background on that screen can be made transparent:

DUAL: tabs on the second screen

tabLayout.useTransparentBackground = true


If set to true, the displayPosition can be set to DisplayPosition.START or DisplayPosition.END with a fling gesture on the component.

tabLayout.allowFlingGesture = true

The same can be obtained using the 'app:allowFlingGesture` attribute: