I like the content area swiping, because it is more ergonomic. Most users hold the phone in one hand and use ther thumb to navigate. Reaching the header with thumb is not easy and not ergonomic.
We need to make possible to use controls what capture the swipe gestures in the tabs.
I know that event handling in QML component is different than in many other components, but I would expect the events handled in a specific order. If a control can and wants to use an input than it must be possible. If a control does not use an input than the input should be passed to the "parent" of the control. So In my opinion the swipe should be the default tab switching input gesture unless there is a control in the tab what can capture and use the swipe. That is exactly how the Shell lenses work. The swipe input switches between lenses, but if the user swipes on a carousel (people, music, etc) then the carousel captures the swipe and does what it suppose to do.
Just for the sake of clarity :)
I like the content area swiping, because it is more ergonomic. Most users hold the phone in one hand and use ther thumb to navigate. Reaching the header with thumb is not easy and not ergonomic.
We need to make possible to use controls what capture the swipe gestures in the tabs.
I know that event handling in QML component is different than in many other components, but I would expect the events handled in a specific order. If a control can and wants to use an input than it must be possible. If a control does not use an input than the input should be passed to the "parent" of the control. So In my opinion the swipe should be the default tab switching input gesture unless there is a control in the tab what can capture and use the swipe. That is exactly how the Shell lenses work. The swipe input switches between lenses, but if the user swipes on a carousel (people, music, etc) then the carousel captures the swipe and does what it suppose to do.