Details
-
Bug
-
Resolution: Cannot Reproduce
-
P3: Somewhat important
-
None
-
5.11.2, 5.12
Description
I am using a TabBar in combination with a StackLayout.
When clicking through the tabs, sometimes the StackLayout does not switch to the corresponding view.
Instead, the TabButton appears selected, but not completely pressed. Pressing a second time, or clicking any other tab, causes the originally selected tab to be displayed.
Sometimes it works fine initially then starts showing the bad behavior. If I leave it alone for a while, it often starts behaving correctly for a bit, but repeatably falls back to the bad behavior.
The behavior is similar to what is described in these existing bugs (but I'm not using Flickables):
QTBUG-60357TabBar/SwipeView sometimes not working correctly inside Flickable- QTBUG-59839 Touchpad: nested Flickables get stuck in pressed state on macOS
- I see this same behavior: "...tab bar button changes color to represent it's been clicked, and the currentIndex and currentItem are triggered and indeed do switch to the correct values. It seems like the view itself is not updated."
The attached QML file demonstrates the issue, but only on target hardware. Works fine on desktop.
Attachments
Issue Links
- relates to
-
QTBUG-59839 Touchpad: nested Flickables get stuck in pressed state on macOS
- Open
-
QTBUG-60357 TabBar/SwipeView sometimes not working correctly inside Flickable
- Closed