[BUG] Frontend switch not set according to SELKIES_USE_CSS_SCALING=True setting

[baxerus]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

If the SELKIES_USE_CSS_SCALING is set to "True" the scaling is used and shown correct.
But the frontend switch that allows changing the setting "HiDPI something" (not sure what exactly it is called in english since my fronend is not running in english is still switched to it's on state.

Maybe this information is not communicated to the frontend at all?
If it is, then the info is not properly used to set the switches state (the setting and the switch state are also opposite. Also the names do not match at all 😐)

Expected Behavior

If SELKIES_USE_CSS_SCALING=True also the "HiDPI something" switch in Off on first connect.

Steps To Reproduce

1. Start a container with the SELKIES_USE_CSS_SCALING env set to True.
2. Connect the browser
3. Open the side panel and check the "HiDPI something"

Environment

- OS: Ubuntu 24.04.3 LTS
- How docker service was installed: packagemanager

Docker creation

Every working `docker` command, but with `-e SELKIES_USE_CSS_SCALING="True"` in it :wink:

Container logs

-

[thelamer]

Yeah it is reversed server side vs clientside settings. True means it is not in HiDPI mode it scales the canvas using the CSS resolution of the page not DPR (device pixel ratio) adjusted. This is one of those settings that cannot actually be locked as the client can send any resolution it wants to the server, but we do pass it down and honor it.
The only true way to lock a client to a resolution is the manual resolution mode, the server ignores resize requests and sends at that res all the time.

[baxerus]

The setting is honored. So the client is getting "low" (as in not full) resolution and scaling it, as it should (tried this with incognito browser).

What is wrong, is, that the client shows the switch state wrong. It is getting low resolution and scaling client-side, but the switch shows "HiDPI ..." is on (blue).
Also when the switch is toggled to off nothing happens. As it should, since then setting and reality is in sync again. Than toggling a second time (back to on) the resolution changes to high DPI (as it should).

This issue is only about the initial state (after page reload) on client side's switch is wrong (not more, the functionality in general working as I would expect it).