Insert in type number the same way as strings

[bnjamin]

When setting the value in an input of type number, set it the same way as a text, so that we get events(keydown, keypressed, keyup) for each "char" in the number when it is converted to a string

[route]

I wonder what would be other drivers default behaviour on this. It definitely needs a test in case we want to merge it.
But this requires a bit more research before any action and it was the reason it got stalled.

[route]

Revisited this — thanks for the patch. Unfortunately removing number from the bulk-set branch breaks negative and decimal values, because <input type="number"> sanitizes its .value on every set, not just on blur: an incomplete numeric string like "-" gets silently reset to "" by the browser. The char-by-char loop in the else branch builds the value via node.value + char, so typing -100 goes:

• set - → sanitized to ""
• set "" + "1" → "1"
• set "10", then "100"

Final value ends up "100" — the sign is silently dropped. Same failure mode for anything starting with . (e.g. .5) or using e notation. This regresses the existing spec covering negative number input (session_spec.rb, "accepts negatives in a number field").

The underlying goal (firing real per-keystroke keydown/keypress/keyup events for number inputs, matching other drivers) is worth doing, but it needs an implementation that accumulates the typed string separately from node.value and only assigns the final value once complete (still firing the synthetic key events per character along the way), plus test coverage for negatives/decimals/scientific notation. Closing this version for now — happy to review a follow-up PR that handles the sanitization case.

Ideally I'd like Cuprite to send real events like Selenium theoretically does but this is a research field to find and compare.