Files
archived-camoufox/python/tests
226ce31c48 Keep the display when repairing a zoomed devicePixelRatio (#1003)
* coherence: keep the display when repairing the ratio

fpgen records some ratios with a browser zoom folded in (1.0909 for
110%), which shrank every CSS size by the zoom. The repair moved the
ratio to the nearest display mode but kept the shrunken sizes, so an
identity drawn from a 1920x1080 monitor claimed a 1760x990 one at
100%. The browser renders at the claimed ratio on the real display,
so a fullscreen window measured 1920x1080 against screen.width 1760
(measured on WSLg). Rescale the CSS geometry with the ratio so the
screen is still the display it was recorded on.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* coherence: a caller's screen is never rescaled

The ratio repair's rescale treated the screen and window sizes as keys
it repairs, so a caller who set them blocked the whole repair: a
1.0909 ratio drawn beside a caller's screen stayed unrepaired, and a
caller's own ratio was reported as screen.width, screen.height and
window.devicePixelRatio instead of the one key that is incoherent.
Rules now name the keys they only adjust; a caller who set any of
them keeps all of them, and the repair runs or is blocked on its own
keys alone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* launch: a zoomed fpgen ratio claims its display

fpgen.yml leaves devicePixelRatio unmapped, so a drawn ratio with a
browser zoom folded in (1.0909 for 110%) left the screen at the
zoomed CSS sizes while the page reported the rendering scale: a
1920x1080 monitor was claimed as a 1760x990 one at 1, and a
fullscreen window on the real display measured 1920x1080 against
screen.width 1760 (measured on WSLg). The coherence rescale
never saw the ratio. A drawn ratio no display mode offers now goes
through that repair at launch, before the display clamp and the
available area are derived from the screen; real scales stay
unmapped as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* launch: a zoomed ratio follows the caller's scale

The zoom repair moved a zoom-folded fpgen ratio to the nearest display
step even when the caller set layout.css.devPixelsPerPx. The page then
rendered at the caller's scale but reported the step: on Windows with
the pref at 1 and 1.818 drawn, devicePixelRatio 1.75 while
matchMedia('(resolution: 1dppx)') matched, a pairing no Firefox has.
font-fallback-windows.py, which pins 1, failed on such draws. The
repair now targets the caller's scale, rescaling the geometry to it,
in both launchers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* driven-wheel-notches: expect a half-pixel line at devicePixelRatio 2

With the zoomed ratio repaired, a macOS identity can land on a ratio
of 2, where the scroller's line height is 29 device px = 14.5 CSS px.
Stock scrolls that fraction and rounds it only in the legacy events
(EventStateManager: CSSIntSize::FromAppUnitsRounded, "We don't deal
with fractional amount in legacy event"), so the guard expected 15 per
line from MozMousePixelScroll and failed on 14.5. It now compares the
scroll with the measured line height and checks the legacy events
carry it rounded.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: coffeegrind123 <bsutherland747@gmail.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Jake Writer <jake_writer@jobharvest.com>
2026-11-10 18:42:11 +00:00
..
2026-10-06 19:10:22 -06:00