selectionStart/selectionEnd on input type=”number” no longer allowed in Chrome

by

Selection is only permitted with text/search, URL, tel and password. The likely reason that selection has been disabled for inputs of type number is that on some devices, or under some circumstances (e.g., when the input has been is presented as a short list), there might not be a caret. The only solution I have found was to change the input type to text (with appropriate pattern to restrict input). I am still looking for a way to do with without changing the input type and will post an update when I find something.

More Related Contents:

  1. How can I get the current Crome URL?
  2. How can I make setInterval also work when a tab is inactive in Chrome?
  3. Allow Google Chrome to use XMLHttpRequest to load a URL from a local file
  4. Setting HTML5 audio position
  5. Why is {} + {} no longer NaN in Chrome console?
  6. new Date() is working in Chrome but not Firefox
  7. Cryptic “Script Error.” reported in Javascript in Chrome and Firefox
  8. How to prevent “The play() request was interrupted by a call to pause()” error?
  9. Contexts and methods for communication between the browser action, background scripts, and content scripts of chrome extensions?
  10. Chrome Extension: Get Page Variables in Content Script
  11. Open IE browser in Firefox/Chrome page
  12. Cannot access cssRules from local css file in Chrome 64
  13. When using setInterval, if I switch tabs in Chrome and go back, the slider goes crazy catching up
  14. How to pass a function in Puppeteers .evaluate() method?
  15. how to set DOM Breakpoints in chrome
  16. CORS not working on Chrome
  17. Does extension messaging like chrome.runtime.sendMessage internally use JSON.stringify?
  18. Force window.open() to create new tab in chrome
  19. Why is a function declaration within a condition block hoisted to function scope in Chrome but not Firefox?
  20. How to get errors stack trace in Chrome extension content script?
  21. Why are function declarations handled differently in different browsers?
  22. Chrome violation : [Violation] Handler took 83ms of runtime
  23. Pass a variable from content script to popup
  24. Making a window pop under in chrome
  25. Synchronous console logging in Chrome
  26. Re-enabling window.alert in Chrome
  27. iframe not reading cookies in Chrome
  28. Keycode is always zero in Chrome for Android
  29. Disable chrome react DevTools for production
  30. How to use “segments” mode at SourceBuffer of MediaSource to render same result at Chomium, Chorme and Firefox?

Leave a Comment