Disable scrolling on `<input type=number>`

JavascriptCssHtmlForms

Javascript Problem Overview


Is it possible to disable the scroll wheel changing the number in an input number field? I've messed with webkit-specific CSS to remove the spinner but I'd like to get rid of this behavior altogether. I like using type=number since it brings up a nice keyboard on iOS.

Javascript Solutions


Solution 1 - Javascript

Prevent the default behavior of the mousewheel event on input-number elements like suggested by others (calling "blur()" would normally not be the preferred way to do it, because that wouldn't be, what the user wants).

BUT. I would avoid listening for the mousewheel event on all input-number elements all the time and only do it, when the element is in focus (that's when the problem exists). Otherwise the user cannot scroll the page when the mouse pointer is anywhere over a input-number element.

Solution for jQuery:

// disable mousewheel on a input number field when in focus
// (to prevent Chromium browsers change the value when scrolling)
$('form').on('focus', 'input[type=number]', function (e) {
  $(this).on('wheel.disableScroll', function (e) {
    e.preventDefault()
  })
})
$('form').on('blur', 'input[type=number]', function (e) {
  $(this).off('wheel.disableScroll')
})

(Delegate focus events to the surrounding form element - to avoid to many event listeners, which are bad for performance.)

Solution 2 - Javascript

One event listener to rule them all

This is similar to @Simon Perepelitsa's answer in pure js, but a bit simpler, as it puts one event listener on the document element and checks if the focused element is a number input:

document.addEventListener("wheel", function(event){
    if(document.activeElement.type === "number"){
	    document.activeElement.blur();
    }
});

If you want to turn off the value scrolling behaviour on some fields, but not others just do this instead:

document.addEventListener("wheel", function(event){
    if(document.activeElement.type === "number" &&
       document.activeElement.classList.contains("noscroll"))
    {
	    document.activeElement.blur();
    }
});

with this:

<input type="number" class="noscroll"/>

If an input has the noscroll class it wont change on scroll, otherwise everything stays the same.

Test here with JSFiddle

Solution 3 - Javascript

$(document).on("wheel", "input[type=number]", function (e) {
    $(this).blur();
});

Solution 4 - Javascript

You can simply use the HTML onwheel attribute.

This option have no effects on scrolling over other elements of the page.

And add a listener for all inputs don't work in inputs dynamically created posteriorly.

Aditionaly, you can remove the input arrows with CSS.

input[type="number"]::-webkit-outer-spin-button, 
input[type="number"]::-webkit-inner-spin-button {
    -webkit-appearance: none;
    margin: 0;
}
input[type="number"] {
    -moz-appearance: textfield;
}

<input type="number" onwheel="this.blur()" />

Solution 5 - Javascript

input = document.getElementById("the_number_input")
input.addEventListener("mousewheel", function(event){ this.blur() })

http://jsfiddle.net/bQbDm/2/

For jQuery example and a cross-browser solution see related question:

https://stackoverflow.com/questions/5669207/html5-event-listener-for-number-input-scroll-chrome-only

Solution 6 - Javascript

I have an alternative suggestion. The problem I see with most of the common recommendation of firing a blur event is that it has unexpected side-effects. It's not always a good thing to remove a focus state unexpectedly.

Why not this instead?

<input type="number" onwheel="return false;" />

It's very simple and straight-forward, easy to implement, and no side-effects that I can think of.

Solution 7 - Javascript

@Semyon Perepelitsa

There is a better solution for this. Blur removes the focus from the input and that is a side affect that you do not want. You should use evt.preventDefault instead. This prevents the default behavior of the input when the user scrolls. Here is the code:

input = document.getElementById("the_number_input")
input.addEventListener("mousewheel", function(evt){ evt.preventDefault(); })

Solution 8 - Javascript

For anyone working with React and looking for solution. I’ve found out that easiest way is to use onWheelCapture prop in Input component like this:

onWheelCapture={e => { e.target.blur() }}

Solution 9 - Javascript

First you must stop the mousewheel event by either:

  1. Disabling it with mousewheel.disableScroll
  2. Intercepting it with e.preventDefault();
  3. By removing focus from the element el.blur();

The first two approaches both stop the window from scrolling and the last removes focus from the element; both of which are undesirable outcomes.

One workaround is to use el.blur() and refocus the element after a delay:

$('input[type=number]').on('mousewheel', function(){
  var el = $(this);
  el.blur();
  setTimeout(function(){
    el.focus();
  }, 10);
});

Solution 10 - Javascript

Typescript Variation

Typescript needs to know that you're working with an HTMLElement for type safety, else you'll see lots of Property 'type' does not exist on type 'Element' type of errors.

document.addEventListener("wheel", function(event){
  const numberInput = (<HTMLInputElement>document.activeElement);
  if (numberInput.type === "number") {
    numberInput.blur();
  }
});

Solution 11 - Javascript

ReactJS Solution

For those needing a React solution, here's an onWheel handler for your type="number" input to prevent the number from changing and prevent the page from scrolling while the user tries to wheel over the input. Finally, it'll refocus on the input so the user can keep editing as intended:

const numberInputOnWheelPreventChange = (e) => {
  // Prevent the input value change
  e.target.blur()

  // Prevent the page/container scrolling
  e.stopPropagation()

  // Refocus immediately, on the next tick (after the current function is done)
  setTimeout(() => {
	e.target.focus()
  }, 0)
}

return <input type="number" onWheel={numberInputOnWheelPreventChange}/>

Solution 12 - Javascript

Easiest solution is to add onWheel={ event => event.currentTarget.blur() }} on input itself.

Solution 13 - Javascript

The provided answers do not work in Firefox (Quantum). The event listener needs to be changed from mousewheel to wheel:

$(':input[type=number]').on('wheel',function(e){ $(this).blur(); });

This code works on Firefox Quantum and Chrome.

Solution 14 - Javascript

If you want a solution that doesn’t need JavaScript, combining some HTML functionality with a CSS pseudo-element does the trick:

span {
  position: relative;
  display: inline-block; /* Fit around contents */
}

span::after {
  content: "";
  position: absolute;
  top: 0; right: 0; bottom: 0; left: 0; /* Stretch over containing block */
  cursor: text; /* restore I-beam cursor */
}

/* Restore context menu while editing */
input:focus {
  position: relative;
  z-index: 1;
}

<label>How many javascripts can u fit in u mouth?
  <span><input type="number" min="0" max="99" value="1"></span>
</label>

This works because clicking on the contents of a <label> that’s associated with a form field will focus the field. However, the “windowpane” of the pseudo-element over the field will block mousewheel events from reaching it.

The drawback is that the up/down spinner buttons no longer work, but you said you had removed those anyway.


In theory, one could restore the context menu without requiring the input to be focused first: :hover styles shouldn’t fire when the user scrolls, since browsers avoid recalculating them during scrolling for performance reasons, but I haven’t thoroughly cross-browser/device tested it.

Solution 15 - Javascript

In my case, I needed to maintain focus and still apply the scroll. None of the solutions above can handle that and doing blur/focus feels a bit hacky to me.

This maintains existing focus and also keeps the scroll. You know... like the browser should. Only minimally tested in chrome and only supports Y-axis.

// you could make this target a specific input instead of document
document.addEventListener('wheel', event => {
  if (!event.target) return;
  const isNumberInput = event.target.nodeName === 'INPUT' && event.target.type === 'number';
  const isFocused = event.target === document.activeElement;
  if (isNumberInput && isFocused) {
    // prevent stupid input change
    event.preventDefault();
    // since we're taking over scrolling, we want to make sure
    // nothing else gets the event
    event.stopPropagation();
    // finally we reapply the scroll
    applyScroll(event);
  }
}, { passive: false });

// this walks up the tree for event.target to find the first
// scrollable parent.  this is probably good enough for most situations.
const applyScroll = event => {
  try {
    // console.debug('attempting to reapply scroll. searching for scrollable container...');
    let scrollContainer = event.target;
    while (scrollContainer && scrollContainer !== document.body && !elementIsScrollable(scrollContainer)) {
      scrollContainer = scrollContainer.parentElement;
      // console.debug('\t-> container was not scrollable. checking parent', scrollContainer);
    }
    if (scrollContainer) {
      // console.debug('scrollContainer container found. applying scroll', scrollContainer, event.deltaY);
      scrollContainer.scrollBy({ top: event.deltaY });
    }
    else {
      // console.debug('no scrollContainer found');
    }
  }
  catch (err) {
    console.info('failed to reapply scroll', err, event);
  }
};

const elementIsScrollable = element => {
  const { scrollHeight = 0, offsetHeight = 0 } = element;
  const scrollable = style.overflowY === 'auto' || style.overflowY === 'scroll';
  return scrollable && scrollHeight > 0 && offsetHeight > 0 && element.scrollHeight > element.offsetHeight;
};

Solution 16 - Javascript

While trying to solve this for myself, I noticed that it's actually possible to retain the scrolling of the page and focus of the input while disabling number changes by attempting to re-fire the caught event on the parent element of the <input type="number"/> on which it was caught, simply like this:

e.target.parentElement.dispatchEvent(e);

However, this causes an error in browser console, and is probably not guaranteed to work everywhere (I only tested on Firefox), since it is intentionally invalid code.

Another solution which works nicely at least on Firefox and Chromium is to temporarily make the <input> element readOnly, like this:

function handleScroll(e) {
  if (e.target.tagName.toLowerCase() === 'input'
    && (e.target.type === 'number')
    && (e.target === document.activeElement)
    && !e.target.readOnly
  ) {
      e.target.readOnly = true;
      setTimeout(function(el){ el.readOnly = false; }, 0, e.target);
  }
}
document.addEventListener('wheel', function(e){ handleScroll(e); });

One side effect that I've noticed is that it may cause the field to flicker for a split-second if you have different styling for readOnly fields, but for my case at least, this doesn't seem to be an issue.

Similarly, (as explained in James' answer) instead of modifying the readOnly property, you can blur() the field and then focus() it back, but again, depending on styles in use, some flickering might occur.

Alternatively, as mentioned in other comments here, you can just call preventDefault() on the event instead. Assuming that you only handle wheel events on number inputs which are in focus and under the mouse cursor (that's what the three conditions above signify), negative impact on user experience would be close to none.

Solution 17 - Javascript

function fixNumericScrolling() {
$$( "input[type=number]" ).addEvent( "mousewheel", function(e) {
	stopAll(e);		
} );
}

function stopAll(e) {
if( typeof( e.preventDefault               ) != "undefined" ) e.preventDefault();
if( typeof( e.stopImmediatePropagation     ) != "undefined" ) e.stopImmediatePropagation();
if( typeof( event ) != "undefined" ) {
	if( typeof( event.preventDefault           ) != "undefined" ) event.preventDefault();
	if( typeof( event.stopImmediatePropagation ) != "undefined" ) event.stopImmediatePropagation();
}

return false;
}

Solution 18 - Javascript

Most answers blur the number element even if the cursor isn't hovering over it; the below does not

document.addEventListener("wheel", function(event) {
  if (document.activeElement.type === "number" &&
    document.elementFromPoint(event.x, event.y) == document.activeElement) {
    document.activeElement.blur();
  }
});

https://jsfiddle.net/s06puv3j/1/

Solution 19 - Javascript

I was struggling with the solution. So, This and other posts help me to do this. We need to change some stuff regarding the best answer here. So in order to disable scrolling, we must add the following:

<script>
$(document).ready(function() {
    $('input[type=number]').on('wheel',function(e){ $(this).blur(); }); 
});
</script>

Instead of using "onwheel" we use "wheel" :)

Solution 20 - Javascript

Antd / React + Typescript answer

    const myComponent = () => {
      const inputRef: React.RefObject<HTMLInputElement> = createRef();
      
      return <Input
         ref={inputRef}
         type="number"
         onWheel={(e) => {
           if (inputRef && inputRef.current && inputRef.current.blur) {
             inputRef.current.blur();
           }
           e.preventDefault();
          }}
      />
    }

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
Questionkjs3View Question on Stackoverflow
Solution 1 - JavascriptGrantzauView Answer on Stackoverflow
Solution 2 - JavascriptPeter RakmanyiView Answer on Stackoverflow
Solution 3 - JavascriptstovrozView Answer on Stackoverflow
Solution 4 - JavascriptMaikon MatheusView Answer on Stackoverflow
Solution 5 - JavascriptSimon PerepelitsaView Answer on Stackoverflow
Solution 6 - JavascriptAustin GilView Answer on Stackoverflow
Solution 7 - JavascriptDibranView Answer on Stackoverflow
Solution 8 - JavascriptAleš ChromecView Answer on Stackoverflow
Solution 9 - JavascriptJames EJView Answer on Stackoverflow
Solution 10 - JavascriptvinylView Answer on Stackoverflow
Solution 11 - Javascriptlwdthe1View Answer on Stackoverflow
Solution 12 - JavascriptTSlegaitisView Answer on Stackoverflow
Solution 13 - JavascriptMathias BankView Answer on Stackoverflow
Solution 14 - JavascriptTigtView Answer on Stackoverflow
Solution 15 - JavascriptCory MawhorterView Answer on Stackoverflow
Solution 16 - JavascriptRimas KudelisView Answer on Stackoverflow
Solution 17 - JavascriptsybView Answer on Stackoverflow
Solution 18 - JavascriptWarren SpencerView Answer on Stackoverflow
Solution 19 - JavascriptDANIEL ROSAS PEREZView Answer on Stackoverflow
Solution 20 - Javascriptuser1101791View Answer on Stackoverflow