v1.7.1
Patch release: a single user-reported bugfix, no new scope.
Fixed
- The wasm demo's canvas rendered at a smaller, fixed 2x scale instead of the 3x
INITIAL_SCALEnative launches at.App::create_windowspecial-casedwasm32to a hardcoded
(512.0, 448.0)LogicalSize, deferring toweb/index.html's own CSS (512x448) — but
winit's web backend actually resizes the attached<canvas>to match the requested inner size,
overriding that CSS regardless. RustyNES's owncreate_windowrequestsNES_W * INITIAL_SCALE
unconditionally (native and wasm alike), which is why its own demo already rendered at 3x — a
user comparing the two demos side by side noticed the size difference.web/index.html's CSS
updated to896x728(the new pre-JS fallback appearance, matching the actual chrome-padded 3x
size) so there's no flash of the old size before winit applies the real one. Found in review
(#82): the fallback CSS's fixed height paired withmax-width: 96vwwould have distorted the
canvas on narrow viewports — switched toaspect-ratio+height: autoinstead.