Skip to content
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

Expander with a nested expander #3803

Closed
offan opened this issue May 21, 2020 · 3 comments
Closed

Expander with a nested expander #3803

offan opened this issue May 21, 2020 · 3 comments
Assignees
Labels
Milestone

Comments

@offan
Copy link

offan commented May 21, 2020

When a nested expander closes, the upper expander close.
Example
` <Expander
ExpandDirection="Down"

                        Header="Hidden Stuff">

                        <StackPanel Orientation="Vertical">

                            <TextBlock Text="...42" />

                            <Expander

                                 ExpandDirection="Down"

                                Header="Hidden Stuff1">

                                <StackPanel Orientation="Vertical">

                                    <TextBlock  Text="...43" />

                                </StackPanel>

                            </Expander>

                        </StackPanel>

                    </Expander>`
@batzen
Copy link
Collaborator

batzen commented May 21, 2020

Would you mind posting the versions you are currently using? May i ask why you didn't follow the bug report template?

@offan
Copy link
Author

offan commented May 21, 2020

Sorry.

  • MahApps.Metro version last commit hash: 4eb4668
  • OS: Win10 1909
  • Visual Studio 2019 16.6.0
  • .NET Framework 4.7.1
    Screenshot:
    1

1

@punker76 punker76 added the Bug label May 21, 2020
@punker76 punker76 self-assigned this May 21, 2020
@punker76 punker76 added this to the 2.0.0 milestone May 21, 2020
punker76 added a commit that referenced this issue May 21, 2020
…ed Expander inside

The problem here is that the first parent Expander also get the Expanded and Collapsed events. So we must look for the OriginalSource which must be also the sender.
@punker76
Copy link
Member

@offan Thanks for reporting this nasty behavior. This will be fixed in next release (final release).

The problem here is that the first parent Expander also get the Expanded and Collapsed events. So we must look for the OriginalSource which must be also the sender.

/cc @batzen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants