-
Notifications
You must be signed in to change notification settings - Fork 16.9k
fix: offscreen rendering with correct screen info. #48730
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
Conversation
4bce604 to
d9cbb87
Compare
7be4173 to
230c136
Compare
230c136 to
c9a426f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
|
API LGTM |
dee50ee to
7d86785
Compare
|
@reitowo can you rebase this PR? Hopefully now with the quiet period over, we can get this PR moving forward. |
f031156 to
a4727ae
Compare
|
@reitowo needs another rebase i think |
c690b2e to
c7ba5c5
Compare
c7ba5c5 to
fee59dd
Compare
|
Rebased. |
|
@MarshallOfSound Could we skip the check as Windows arm64 & amd64 is failling alternatively. |
|
Release Notes Persisted
|
|
I was unable to backport this PR to "40-x-y" cleanly; |
|
I have automatically backported this PR to "41-x-y", please check out #49494 |
Description of Change
Previously OSR doesn't have a valid screen info, the media query of
(device-width: 1920px)will be always invalid. This fix partially checked CEF's implementation and made some modification so that theOffScreenRenderWidgetHostViewcan update correct screen info based on OSR window's size and scale factor.Closes #47835
Checklist
npm testpassesRelease Notes
Notes:
webPreference.offscreen.deviceScaleFactorto allow user specify a value, instead of using user's primary display's value.