Lively Wallpaper picks up wrong scaling factor for the second monitor #1996
Comments
|
Chromium switched to Possible ways to fix this:
I am leaning towards (1) at the moment, will try (2) and (3) first but that will require some testing. |
|
Tried to manually install v2.0.7.0, the scaling is 100%. But sometimes the wallpaper disappears as mentioned in v2.0.7.4 changelog. I'm not sure about (1). It might break someone else's setup. Probably the easiest way is adding an advanced option to allow users manually override the scaling factor. |
This comment was marked as outdated.
This comment was marked as outdated.
|
Thanks. Currently I don't see there's any potential bug. |
|
Having the same issue, glad you guys can reproduce it, it was driving me insane trying to figure out what was going on. In case is useful: This is my display arrangement: When the screensaver comes up uses like a half of the screen only. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as outdated.
This comment was marked as outdated.
|
@momoe The rain issue is unrelated to this issue and more about how the page code handles scale factor, it behaves the same as you change browser scale and will require wallpaper code change. Can verify on chrome: https://www.rocksdanister.com/rain I can't seem to reproduce the original issue on my side with triple monitor at different scale settings on the beta build of Lively. <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Browser Info</title>
<style>
body {
font-family: Arial, sans-serif;
margin: 20px;
}
.info {
margin: 10px 0;
}
.label {
font-weight: bold;
}
</style>
</head>
<body>
<h1>Browser Information</h1>
<div class="info">
<span class="label">Scale Factor:</span>
<span id="scaleFactor"></span>
</div>
<div class="info">
<span class="label">Screen Resolution:</span>
<span id="screenResolution"></span>
</div>
<div class="info">
<span class="label">Browser Window Size:</span>
<span id="windowSize"></span>
</div>
<div class="info">
<span class="label">User Agent:</span>
<span id="userAgent"></span>
</div>
<div class="info">
<span class="label">Browser Version:</span>
<span id="browserVersion"></span>
</div>
<script>
function getScaleFactor() {
return window.devicePixelRatio;
}
function getScreenResolution() {
return `${window.screen.width} x ${window.screen.height}`;
}
function getWindowSize() {
return `${window.innerWidth} x ${window.innerHeight}`;
}
function getUserAgent() {
return navigator.userAgent;
}
function getBrowserVersion() {
let userAgent = navigator.userAgent;
let match = userAgent.match(/(Chrome|Firefox|Safari|Edge)\/(\d+)/);
if (match) {
return `${match[1]} ${match[2]}`;
}
return 'Unknown';
}
document.getElementById('scaleFactor').textContent = getScaleFactor();
document.getElementById('screenResolution').textContent = getScreenResolution();
document.getElementById('windowSize').textContent = getWindowSize();
document.getElementById('userAgent').textContent = getUserAgent();
document.getElementById('browserVersion').textContent = getBrowserVersion();
</script>
</body>
</html> |
I'm still getting the wrong scaling with this beta version. This time, copying the old |
|
Yes, old cef wont work with newer builds. How are you testing to verify the scaler issue? |
Describe the bug
I have a main monitor, 3840x2160 at 200%, and a side screen, 480x1920 at 100%. I've been using Lively Wallpaper for a long time, until a recent update from Microsoft store break everything. Looks like lively wallpaper is picking up the scaling factor from the main monitor and scales the html page on the side screen at 200%.
To Reproduce
You need two monitors to trigger this.
Expected behavior
It should pick up the corresponding scaling factor of the monitor.
Screenshots/Video
Desktop (please complete the following information):
Additional context
Should be related to a recent commit.
Log file (Important)
lively_log_20231110_143736.zip
The text was updated successfully, but these errors were encountered: