Skip to content

DomainUpDown and NumericUpDown allow height changes in VisualStylesMode.Net11 instead of reverting to the original height #15210

Description

@Olina-Zhang

.NET version

.NET 11 SDK build: 11.0.100-rtm.26477.103

Did it work in .NET Framework?

Not tested/verified

Did it work in any of the earlier releases of .NET Core or .NET 5+?

New APIs in .NET 11

Issue description

When VisualStylesMode is set to Net11, the DomainUpDown and NumericUpDown controls allow their Height property to be changed through the Visual Studio Properties window.
This behavior is inconsistent with VisualStylesMode = Classic. In Classic mode, after entering a different Height value and pressing Enter, the value immediately reverts to the control's original height.
In Net11 mode, however, the new height is accepted and the control is resized in the Designer. After closing and reopening the Form Designer, the control returns to its original height.
The behavior in Net11 mode should be consistent with Classic mode and should not accept a height value that cannot be preserved.

VisualStylesMode: NET11

DomainUpDown_Height_NET11.mp4

VisualStylesMode: Classic

DomainUpDown_Height_Classic.mp4

Steps to reproduce

  1. Create a WinForms project and open a form in the Form Designer.
  2. Set VisualStylesMode to Net11.
  3. Add a DomainUpDown and a NumericUpDown control to the form.
  4. Select each control and change its Height value through the Visual Studio Properties window.
  5. Press Enter after entering the new height value.
  6. Observe the height value and the controls in the Designer.
  7. Close and reopen the Form Designer.

Actual Result:
With VisualStylesMode set to Net11, the new height value is accepted after pressing Enter. However, after closing and reopening the Form Designer, the DomainUpDown and NumericUpDown controls revert to their original heights.

Expected Result:
The behavior should be consistent with VisualStylesMode = Classic. When changing the Height value through the Properties window and pressing Enter, the value should immediately revert to the control's original valid height rather than accepting a height that cannot be preserved.

Activity

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

Metadata

Metadata

Assignees

Labels

NewApi-Net11Tracks issues for public APIs targeted for .NET 11.untriagedThe team needs to look at this issue in the next triage

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions