Description

When a user selects text in a readonly VNumberInput and types a non-digit character (e.g. a space or letter), the onBeforeinput handler would still fire. Inside that handler, when the typed character doesn't match the allowed pattern, the code calls:

e.preventDefault()
inputElement!.value = potentialNewNumber  // empty string when invalid chars replace all text
nextTick(() => inputText.value = potentialNewNumber)

This inadvertently sets inputText to an empty string, which the computed setter interprets as clearing the value (model.value = null), breaking the readonly contract.

Fix

Add an early return at the top of onBeforeinput when controlsDisabled (readonly or disabled) is true. This is consistent with how toggleUpDown, clampModel, formatInputValue, and trimDecimalZeros already guard against mutations.

Changes

• VNumberInput.tsx: add if (controlsDisabled.value) return guard to onBeforeinput
• VNumberInput.spec.browser.tsx: add regression test for typing non-digit chars while readonly

Fixes #22677