MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: RasterizationScale is always reported as 1.0 and only later gets updated with correct value

Open
#5,329 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

RasterizationScale is initially reported as 1.0 while it should be larger value (both monitor scaling and text size are > 100%) and only later at some point gets updated with correct value.
I'm aware that I can add event handler to register for rasterization scale changes, however I need to get the correct value on loading because the parent window I'm using to host WebView controller is fixed size with dpi/text scaling adjustments.

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

138.0.3351.109

SDK Version

1.0.1462.37

Framework

Win32

Operating System

Windows 10

OS Version

10.0.19045

Repro steps

Create simple webview2 C++ application like in the getting started samples.
Call ICoreWebView2Controller3::get_RasterizationScale once the WebView controller is created successfully.
Rasterization scale always returned as 1.0 after controller created regardless of real value.

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Win32 getting-started sample and reproduce the call to ICoreWebView2Controller3::get_RasterizationScale immediately after controller creation on Windows 10 with scaling above 100%. Compare the initial value with the later update and determine what initialization behavior should be considered done; the issue names no repository files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.