Resizing cursor showed near caption button when IsResizable=false while ExtendsContentIntoTitleBar=true

[HO-COOH]

Describe the bug

It will show a resizing cursor at the border near the caption button. Other part of the border will not show a resizing cursor.

Steps to reproduce the bug

In the window constructor, use this code

        (AppWindow.Presenter as OverlappedPresenter).IsResizable = false;
        ExtendsContentIntoTitleBar = true;

Expected behavior

Don't show resizing cursor when the window is not resizable.

Screenshots

NuGet package version

WinUI 3 - Windows App SDK 1.5.3: 1.5.240428000

Windows version

Windows 10 (1809): Build 17763

Additional context

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one. Thank you!

Open similar issues:

• Resizable pointer shows up even when a window is maximized (#8665), similarity score: 0.78
• SetBorderAndTitleBar(true, false) with IsResizable = false removes the border although it should remove only the titlebar (#7629), similarity score: 0.78
• Broken hit testing on extended title bar when maximized (#8805), similarity score: 0.76

Closed similar issues:

• mouse pointer change to resize when hovering on top bar and window is maximized (#9353), similarity score: 0.76
• Bug: ExtendsContentIntoTitleBar causes the minimize/maximize button overflow window on win10 (#9354), similarity score: 0.76

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[0x5bfa]

The same happens when you maximize the window.

[codendone]

The issue when the window is maximized is tracked by #8665. I believe that upcoming fix didn't address this IsResizable=false scenario.

[ghost1372]

i tested with v1.6-exp2 and does not fixed yet

ExtendsContentIntoTitleBar = true;
SetTitleBar(AppTitleBar);

((OverlappedPresenter)AppWindow.Presenter).IsResizable = false;

[codendone]

This was closed as fixed/duplicate of #7629. The fix will be in the next 1.6 release.