Jake ArchibaldWatch out! Chrome has a huge bug with <input type="number"> which causes values to change unexpectedly.
It's fixed in Chrome 150, but that won't land until the end of June.
🍁voilà-DCKIM🍁@jaffathecake I have noticed this same thing but, I never considered that it would be a problem, and I also assumed that this was how it has been for a very long time.
Was the scroll wheel functionality implemented in a recent release? I am not clear when it was first implemented.
It's pretty stupid looking, as explained, if you are just scrolling along, the cursor passes over the number box and increments/decrements it.
Just silly stuff...
@dckim I think, in the past, Chrome would alter the value on scroll-wheel, but also block scrolling. Then they fixed that, and regressed with this even-worse UX.