-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Drop-down list (<select>) not displayed correctly in WPF with 125% or 150% display setting #213
Comments
I think this happens because the scale transformation used when there is a non-standard DPI setting isn't applied to popups. I had a poke around in CefSharp.Wpf/WebView.cpp and found I could (apparently) fix the drop-downs by applying the result of GetScaleTransform() to _popup and to the offsets used in SetPopupSizeAndPosition(). |
Hi, We have seen this at a customer site using Windows 8, but I haven't had time to look into it yet. Care to make a PR out of it? It would be great! Many thanks in advance. |
…e layout and offset transforms to popup when display setting has non-standard DPI
Proposed fix for issue #213 (for CefSharp1 only).
Re-targetting CefSharp3 now, so it's not forgotten. |
@JanEggers, they are related but not 100% the same. We should verify that it works w/ CefSharp3 before closing I'd say. If you like, give it a try (by switching DPI in Windows) and see if they are positioned correctly. |
Take a look at this line. I'm note sure it's entirely relevant though (since I changed the dropdowns to work slightly differently on CefSharp3 compared to CefSharp1), so please investigate if you have time and remove the comments if it does work right. |
@perlun I think I cracked the issue, we did need to add similar transformation to the popup to make sure it scaled correctly. |
Fixing #213 popup focus behavior and DPI transform bug.
Closed with merge of #337 |
With Display Settings on 125% or 150%, the drop-down part of a select element is displayed with the incorrect size and position. This applies to v1.25.5.0
The text was updated successfully, but these errors were encountered: