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

[11.1-beta2] Regression: Window System buttons is not visible when ExtendClientAreaToDecorationsHint="True" #15908

Closed
baochenw opened this issue Jun 4, 2024 · 4 comments
Labels

Comments

@baochenw
Copy link
Contributor

baochenw commented Jun 4, 2024

Describe the bug

This is a regression of 11.1-beta2. The issue is not reproducible with 11.1-beta1.
When set ExtendClientAreaToDecorationsHint="True" to MainWindow, the window system buttons (Minimize, Maximize and Close button) are not visible and the window has no border and can't drag move.

To Reproduce

  1. Set ExtendClientAreaToDecorationsHint="True" on MainWindow
  2. Build and start app, the the window system buttons (Minimize, Maximize and Close button) are not visible and the window has no border and can't drag move.
  3. Remove ExtendClientAreaToDecorationsHint="True", the title bar appears.
  4. Keep ExtendClientAreaToDecorationsHint="True" and downgrade to 11.1-beta1, the issue is gone.

Expected behavior

The same behavior to 11.1-beta1

Avalonia version

11.1-beta2

OS

Windows

Additional context

No response

@baochenw baochenw added the bug label Jun 4, 2024
@rabbitism
Copy link
Contributor

rabbitism commented Jun 4, 2024

Should have been fixed by #15552. Can you please help to verify in latest master?

@baochenw
Copy link
Contributor Author

baochenw commented Jun 4, 2024

Close it as it has already fixed by #15552

@baochenw baochenw closed this as completed Jun 4, 2024
@guilhermeolisi
Copy link

I am experiencing the same issue in Avalonia 11.1.2. Will the fix for this issue be included in version 11.1.3?

@malex81
Copy link

malex81 commented Oct 1, 2024

Will the fix for this issue be included in version 11.1.3?

No. Error still reproduced in 11.1.3. Last working wersion is 11.0.13.

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

No branches or pull requests

4 participants