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

Bug: Expander Should Not Have a MaxWidth #4391

Closed
robloo opened this issue Mar 1, 2021 · 1 comment · Fixed by #4394
Closed

Bug: Expander Should Not Have a MaxWidth #4391

robloo opened this issue Mar 1, 2021 · 1 comment · Fixed by #4394
Labels
area-Expander team-Controls Issue for the Controls team

Comments

@robloo
Copy link
Contributor

robloo commented Mar 1, 2021

Describe the bug

Expander has a MaxWidth set in the template:

<Setter Property="MaxWidth" Value="{ThemeResource FlyoutThemeMaxWidth}" />

This prevents HorizontalAlignment = "Stretch" from working (which is also set by default in the style). Instead, just like other controls, MaxWidth should be unset (double.NaN) and HorizontalAlignment = "Left". I can't think of any other content control that constrains width like this.

Steps to reproduce the bug

  1. Add a new Expander control to a page
  2. The expander will not stretch past the MaxWidth

Expected behavior

Expander should stretch as most all other controls do.

Screenshots

Version Info

NuGet package version: 2.6.0 preview

Windows app type:

UWP Win32
Windows 10 version Saw the problem?
Insider Build (xxxxx)
October 2020 Update (19042)
May 2020 Update (19041)
November 2019 Update (18363)
May 2019 Update (18362)
October 2018 Update (17763)
April 2018 Update (17134)
Fall Creators Update (16299)
Creators Update (15063)
Device form factor Saw the problem?
Desktop
Xbox
Surface Hub
IoT

Additional context

@ghost ghost added the needs-triage Issue needs to be triaged by the area owners label Mar 1, 2021
@robloo robloo changed the title Expander Should Not Have a MaxWidth Bug: Expander Should Not Have a MaxWidth Mar 1, 2021
@michael-hawker
Copy link
Collaborator

🦙 Related to #4248.

@robloo robloo mentioned this issue Mar 2, 2021
@ghost ghost added the working on it label Mar 2, 2021
@StephenLPeters StephenLPeters added area-Expander team-Controls Issue for the Controls team and removed needs-triage Issue needs to be triaged by the area owners labels Mar 3, 2021
@ghost ghost removed the working on it label Mar 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Expander team-Controls Issue for the Controls team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants