I\'m building a calculator, and am using the following:
jQuery(function($) {
$(\'#Quantity\').keyup(function() {
console.log($(this).val());
});
It appears because jQuery uses its own event object instead of a native browser one, and in the process of creating this object reads every possible property of an event, including charCode:
props = [ ... "charCode" ... ]
for ( var i = this.props.length, prop; i; ) {
prop = this.props[ --i ];
event[ prop ] = originalEvent[ prop ];
}
Firefox rightly warns you that you don't want to read charCode in the case of keyup events, not realising that you're just copying it, not actually doing anything with it. Consequently any page you create with jQuery keyup/keydown handlers will spit endless warnings.
(IMO, jQuery should not bother copy this property. In the only case you actually want to use it—keypress—you can just use plain old which.)