microsoft / microsoft-ui-xaml

WinUI: a modern UI framework with a rich set of controls and styles to build dynamic and high-performing Windows applications.
MIT License
6.38k stars 683 forks source link

Can't select text from TextBox/AutoSuggestBox set as content in TitleBar with the cursor #9702

Closed eduardobragaxz closed 5 months ago

eduardobragaxz commented 5 months ago

Describe the bug

When using a TextBox/AutoSuggestBox as content in the TitleBar control you can't select the text with the cursor. It drags the window instead. Also, the cursor doesn't change into the caret when hovering the TextBox/AutoSuggestBox.

Steps to reproduce the bug

Create a project with the TitleBar control and add a TextBox/AutoSuggestBox as content and run.

Expected behavior

No response

Screenshots

No response

NuGet package version

WinUI 3 - Windows App SDK 1.6 Experimental 1: 1.6.240531000-experimental1

Windows version

Windows 11 (22H2): Build 22621

Additional context

No response

github-actions[bot] commented 5 months ago

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:

Closed similar issues:

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

ghost1372 commented 5 months ago

footer and header also does not work, all of them calculated as a drag regions

veler commented 5 months ago

Hi,

I reproduce a similar issue. My monitor is on 125% scale. As you can see on the video below, I can click on the Settings button if the mice cursor is some space to the left of it, but not fully hover it.

https://github.com/microsoft/microsoft-ui-xaml/assets/3747805/61805901-358d-4032-b34e-b67e309e7c9c

This issue does NOT reproduce is my monitor scale is at 100%.

ghost1372 commented 5 months ago

@ranjeshj ?

karkarl commented 5 months ago

@veler I am able to repro this issue only if the scale factor has changed, is that the case for you?

karkarl commented 5 months ago

The issue doesn't repro in the experimental2 release, can you try verifying if this resolves your issue? A bunch of PR's were missed in the experimental1 cherry-pick...

ghost1372 commented 5 months ago

@codendone This issue Fixed in v1.6-exp2 and i think this can be closed