MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Problem/Bug]: The WebView display area is smaller than the WebView window size
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
What happened?
The WebView display area is smaller than the WebView window size
Chrome_WidgetWin_0：size: 1203 x 694 ,pos: 0, 0 (0, 67)
Chrome_WidgetWin_1：size:1203 x 694, pos: 0, 0 (0, 67)
Chrome_RenderWidgetHostHWND：size: 1203 x 694 ,pos: 0, 0 (0, 67)
Intermediate D3D Window：size: 1203 x 694, pos: -514, -290 (-514, -223)
Web page display area：size: 557x 328
The offset of the Intermediate D3D Window should be wrong？
WebView2 version：118.0.2088.46
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
118.0.2088.46
SDK Version
No response
Framework
Win32
Operating System
Windows 10
OS Version
No response
Repro steps
- load webview.
- move the parent window.
Regression
Don't know
Last working version (if regression)
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report identifies no repository files, tests, or code entry points. Begin with the Win32 WebView2 setup and the repro steps of loading the WebView and moving its parent window; done means the WebView display area matches the window size after the move.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100