Web NumericTextField snaps its Value to Increment, unlike desktop

A Web NumericTextField silently rewrites its value to the Increment grid. With the default Increment of 1, setting Value = 3.1415 (Minimum 0, Maximum 100, DecimalPlaces 2) stores, displays, and reads back 3 on the web, while the identical control on desktop displays 3.14 and keeps the full 3.1415.

This diverges from desktop semantics in two ways:

• Increment should only be the amount added/subtracted by the up/down buttons. On the web it currently also quantises the stored value: any value that is not a multiple of Increment (anchored at Minimum) is snapped to the nearest step.
• DecimalPlaces should only control how the value is displayed. On the web it currently also rounds the stored value.

Values typed into the running web control are snapped the same way before the app ever sees them, so a Web app cannot hold a value like 3.1415 unless Increment divides it exactly. Web page layouts whose stored value is off the increment grid are also rejected on load.

Expected behaviour (desktop parity): the stored Value is kept at full precision and only clamped to Minimum…Maximum; Increment affects the buttons only; DecimalPlaces and UseGroupingSeparators affect display only.