Bugzilla

(In reply to Ilyas Kaya from comment #17)
> Agreed. I just tested a bunch, and I had to go out of my way to accidentally change the value with a scroll wheel.

I think we're in agreement that there should be some sort of interoperable opt-in mechanism here, per end of comment 16, but I just need to push back gently on this point about this issue being hard to trigger -- even if it's rare, it *does* happen accidentally, at least for some users (including me); and when it does happen, consequences can be pretty terrible and can have real-world consequences. e.g. inadvertently changing digits in your contact info in a web-form where you're urgently expecting a message back; or inadvertently increasing a "quantity" field when placing an order for some expensive item and being billed/shipped the wrong amount; or changing some field in a web-based tax-form where incorrect information has legal and/or financial consequences.

This is particularly bad because the unwanted modification can happen *just after* the user has visually verified that the value is (er, was) correct, e.g. if the user is moving their mouse to hover each field as they visually check it for correctness; and then they scroll down to submit, & inadvertently change the value after they've verified it.

(In reply to Ilyas Kaya from comment #17)
> Agreed. I just tested a bunch, and I had to go out of my way to accidentally change the value with a scroll wheel.

I think we're in agreement that there should be some sort of interoperable opt-in mechanism here, per end of comment 16, but I just need to push back gently on this point about this issue being hard to trigger -- even if it's rare, it *does* happen accidentally, at least for some users (including me); and when it does happen, consequences can be pretty terrible and can have real-world consequences. e.g. inadvertently changing digits in your contact info in a web-form where you're urgently expecting a message back (which will now never arrive since you provided bad contact info); or inadvertently increasing a "quantity" field when placing an order for some expensive item and being billed/shipped the wrong amount; or changing some field in a web-based tax-form where incorrect information has legal and/or financial consequences.

This is particularly bad because the unwanted modification can happen *just after* the user has visually verified that the value is (er, was) correct, e.g. if the user is moving their mouse to hover each field as they visually check it for correctness; and then they scroll down to submit, & inadvertently change the value after they've verified it.