Skip to content

[Bug] Auto-disconnect doesn't work with TabbedPage #36

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
thomasgalliker opened this issue May 16, 2025 · 0 comments · May be fixed by #35 or #34
Open

[Bug] Auto-disconnect doesn't work with TabbedPage #36

thomasgalliker opened this issue May 16, 2025 · 0 comments · May be fixed by #35 or #34
Assignees
Labels
bug Something isn't working

Comments

@thomasgalliker
Copy link
Owner

Description

When SegmentedControls are used in pages which are part of a TabbedPage, the auto-disconnect feature does not seem to work properly. It disconnects handlers when tabs are navigated.

Steps to Reproduce

  1. Create TabbedPage + add tab pages.
  2. Create multiple SegmentedControl instances per tab page.
  3. Navigate from tab page to another tab page.

Expected Behavior

  • Navigation of tabs should not lead to automatic disconnect of SegmentedControlHandlers.

Actual Behavior

  • Navigation of tabs does lead to automatic disconnect of SegmentedControlHandlers.
  • Events are unsubscribed too early which leads to visual impacts in SegmentedControl.

Basic Information

  • Version with issue: 1.4.27-pre
  • Last known good version: N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant