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

[Problem/Bug]: CoreWebView2WindowFeatures/ICoreWebView2WindowFeatures returning invalid values for top and left when provided with negative values in window.open() #4551

Open
mikamikem opened this issue May 10, 2024 · 1 comment
Assignees
Labels
bug Something isn't working priority-low We have considered this issue and decided that we will not be able to address it in the near future. tracked We are tracking this work internally.

Comments

@mikamikem
Copy link

mikamikem commented May 10, 2024

What happened?

The top and left values on ICoreWebView2WindowFeatures and CoreWebView2WindowFeatures appear to be signed integer values that are simply cast to unsigned integer values. If a website uses negative values (which should be invalid for these properties), the values returned are not uint.MaxValue as the docs specify, but a very large uint value that corresponds to the negative value cast to a uint.

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

126.0.2544.0

SDK Version

1.0.1722.45

Framework

WPF

Operating System

Windows 10

OS Version

19045.4355

Repro steps

  1. Go to https://javascript.info/popup-windows#example-a-minimalistic-window
  2. Click the run button on the first example to open a popup with a negative left and top value.
  3. Observe the values returned by CoreWebView2WindowFeatures.Top and CoreWebView2WindowFeatures.Left.

Expected:
Both values should be uint.MaxValue because negative values are invalid for these fields.

Observed
Values are uint.MaxValue - 1000 + 1 which is the signed integer value of -1000 used in the example.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Don't know

Last working version (if regression)

No response

AB#46380638

@mikamikem mikamikem added the bug Something isn't working label May 10, 2024
@johna-ms
Copy link
Contributor

Thanks for reporting this! I can repro this and am adding it to our backlog

@johna-ms johna-ms added the tracked We are tracking this work internally. label May 13, 2024
@github-actions github-actions bot added the priority-low We have considered this issue and decided that we will not be able to address it in the near future. label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-low We have considered this issue and decided that we will not be able to address it in the near future. tracked We are tracking this work internally.
Projects
None yet
Development

No branches or pull requests

2 participants