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

WPF TextBox insertion caret does not render when moved to lower DPI monitor in a PMAv2 process #1774

Closed
SamBent opened this issue Sep 5, 2019 · 3 comments · Fixed by #1949
Assignees
Labels
.NET Framework netfx-servicing-approved Netfx Approved for Servicing rank20 Rank: Priority/rank on a scale of (1..100)
Milestone

Comments

@SamBent
Copy link
Contributor

SamBent commented Sep 5, 2019

  • .NET Core Version: (e.g. 3.0 Preview1, or daily build number, use dotnet --info) 3.0
  • Windows version: (winver) 1803+ (PMAv2 needed)
  • Does the bug reproduce also in WPF for .NET Framework 4.8?: Yes
  • Is this bug related specifically to tooling in Visual Studio (e.g. XAML Designer, Code editing, etc...)? no

Problem description:
[Port of a bugfix in the .NET 4.8 servicing pipeline.]

  1. Have 200% primary, 100% secondary
  2. Launch repro proj exe on primary
  3. Focus the textbox and see the caret blinking
  4. Move it to secondary

Actual behavior:
The caret disappears, but can still type in the textbox

Expected behavior:
The caret doesn't disappear.

Minimal repro:
[Available in .NETFx bug] It's just a WPF app with a TextBox, manifested to request PerMonitorAwareV2.

@grubioe grubioe added this to the 3.1 milestone Sep 5, 2019
@weltkante
Copy link

#1066 might be related (or actually the same)

@vatsan-madhavan
Copy link
Member

#1066 might be related (or actually the same)

It's the same!

@SamBent
Copy link
Contributor Author

SamBent commented Sep 24, 2019

Fixed for 3.1 via #1939.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
.NET Framework netfx-servicing-approved Netfx Approved for Servicing rank20 Rank: Priority/rank on a scale of (1..100)
Projects
None yet
5 participants