It really doesn't look like anything pertaining to client side coding; I've put in some tracers, and nothing seems to be firing during the data entry. My own theory is its the page containing the control.
If there's no javascript firing on the object nor is there any javascript set at the ASCX level that handles keypress/keydown/keyup, then that leaves the ASPX and any master pages to which the ASPX belongs. Load full page up in IE and do view source. Do a search for keypress, keydown and keyup and see if anything springs up. Keystrokes are handled client side, not server side, so there must be a client script somewhere -
embedded in the ASCX HTML code
OR
dynamically added in the code behind for the ASCX
OR
embedded in the ASPX HTML code
OR
dynamically added in the code behind for the ASPX
OR
... you get the picture
...check the ASCX, ASPX and Master pages. Don't forget to check the code behinds for each too. Realise also that a script can be attached to an object at runtime in Javascript without it being in the onlick, onkeypress, onkeydown, onkeyup properties of the object itself - for instance:
- document.onload = function(){
-
var elem = document.getElementById("MyElem")
-
-
elem.onkeypress = function(event){
-
//Do my bidding...
-
}
-
}
This may be added at a higher level than the ASCX, but could still be attached to the object embedded inside. So just because it's not in a user control, doesn't mean it's not there...
4
