Chrome 149 Patches Scroll Bug That Changed Form Values Silently, but Fix Is Incomplete

Google’s Chrome 149 includes a fix for a browser bug that silently altered number fields in web forms as users scrolled, but a Firefox developer says the patch does not cover every scenario.

Jake Archibald, a developer at Mozilla who works on Firefox, said on X that Chrome 149 carries the fix and is rolling out this week — yet the bug persists on pages that attach scroll event listeners to a parent element.

What the Bug Does

The flaw, which first appeared around Chrome 147 according to the Chromium issue tracker, caused the mouse wheel to simultaneously scroll a page and change the value inside a focused number input field — the standard HTML `` element used for quantities, prices, and similar data.

Users scrolling through a form could unknowingly increment or decrement a number field without receiving any alert.

The bug drew enough complaints that Chromium engineers marked it for a fix, then verified the patch in both Chrome 149 test builds and Chrome 150.

Where the Fix Falls Short

Archibald credited developer Bramus for getting the change merged into Chrome 149’s stable release, which Google began rolling out to desktop users this week.

Still, Archibald said the fix does not hold in every situation.

“The bug is still present if a site listens for scroll events on a parent element in a way That Lets the browser keep scrolling freely,” he said.

That scenario is common in complex web applications, which frequently attach scroll listeners to large container elements and nest multiple inputs inside them.

Developers who build or maintain those kinds of apps — dashboards, e-commerce order forms, data-entry tools — may still see unexpected value changes in number fields after updating to Chrome 149.

Who Is at Risk

Standard web pages and simple forms are largely covered by the patch.

By contrast, single-page applications and data-heavy interfaces that rely on custom scroll handling remain exposed until a further fix arrives.

Google has not set a public timeline for addressing the remaining edge case, though Archibald suggested a follow-up patch would likely close it in a future release.

Chrome 150 is expected to reach the stable channel by late June, according to Google's Chrome release schedule.

The flaw underscores a broader challenge browser makers face as JavaScript-heavy web apps push scroll and input event handling far beyond what the browser’s default behavior anticipates.