Detected screen size is still incorrect

[dalgas98]

Detected screen size is incorrect as has been reported before. Accepting current window size by clicking on hi-light gives an error: Please correct errors.

[drcheap]

This is still a mystery as to why it happens, and only for a select few people.

My best suggestion is to go into the Advanced Settings section and increase the Oversize Allowance beyond the default 20% (in your example case the 100% setting should be enough).

[t4k]

MacBook Pro, macOS Sonoma, Built-in Display 1680×1050, Dell U2723QE 2560×1440

My detected screen size is referencing my laptop screen, while I have an external monitor that has a much larger screen size. I can only set values against the built-in display, and oversize allowance does not seem to do anything.

A potential factor might be that the Main Display is set to be the Dell monitor, and the Extended Display is set to be the Built-in screen.

[drcheap]

In the multi-monitor testing I've done, the "detected screen size" matches the monitor the window of the tab with the settings open (assuming it's not overlapping multiple...then there are OS-specific rules as to which one it is effectively on).

This is also something that can be spoofed, such as for privacy or anti-fingerprinting reasons, and thus the add-on sometimes gets bad information. I am considering either removing this "feature" or maybe adding an advanced setting that lets you use some super high value like 99999 as the max size instead of basing it on the detected size.

I'm also surprised that event the highest (500%) oversize allowance doesn't work, that should let you go up to 9900x6300 even on the built-in .

[DJCrashdummy]

i'm not 100% sure if i suffer exact the same issue... but they are at least somewhat related.

as long as my browser window is maximized, the "Current size" is correct. but as soon as the window isn't maximized the mess starts:

• both displayed values at "Current size" are always 52 pixel too big as soon as the window is not maximized. - i have no idea why 52 pixel... 🤷
• if the window is maximized and then changed to a window, the actual window size is what you have set in WindowSizer (although the values of "Current size" are off as already mentioned).
• but now the worst thing: if your window is already not maximized and then change its size (via WindowSizer), the actual window size is 52 pixel too small! ...then the values of "Current size" seem to be correct, but they are not!

-> so unfortunately also the main feature is effected, not just the "Current size" feature.

additional detail:

• in the case of coming from a maximized window, the window seems to get even smaller as the target for the split of a second...
• and in the case of changing from a window size to a different window size, there is a flickering which stops when you click somewhere else to make the browser window not the active one.

---

it's the easiest to spot when you use a resolution (multiple times) which is exact the same as your display: the first time it works correctly (and just the values at "Current size" are off); the second time also the actual size goes wrong (but by the same values, that's why everything seems to be correct if you don't check it properly); the third time noting changes at all.
https://github.com/user-attachments/assets/f8736a15-04c0-4694-a01a-70a38cee90f5
i've attached a video as small presentation of the issue(s): the native resolution of the used screen is 1600x900 and i have one panel with the height of 46 pixel active. - and the flickering only seems to be spotty in the video, IRL it's a constant flickering.

[DJCrashdummy]

BTW: if you try the same with the actual resolution of the maximized window and not the one of your screen, the first step (correct window size but wrong displayed values) gets skipped and it goes directly to the wrong window size with wrong values.

hold on! if you have a set with the actual resolution of your maximized window, the window size goes to the last not maximized resolution (no matter the size) if you use it while the window is maximized! ...very strange. 🤨