# Monday, December 27, 2004
« Tip of the Day: Debugging Javascript in ... | Main | Tip of the Day: Formatting Dates »
Tip of the Day: Determining which control caused the Postback

While not 100%, you can look at the following to see what control caused the postback on a form:

Request.Form("__EVENTTARGET")

It works because ASP.Net uses javascript to handle the postback functionality, and the __EVENTTARGET query string value can contain the name of the control which caused the postback.

Want to know what arguments are being passed during the postback? Take a look at the Request.Form(”__EVENTARGUMENT”) value!

 

All Things | ASP.Net | Tips and Tricks
Monday, December 27, 2004 10:19:36 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [4]  |  Related posts:
Tip of the Day: Testing emails by saving them to files
WinForm Tip: Dynamically change the font color of a ComboBox or ListBox
Tip of the Day: Convert XmlDocument to XDocument
More adventures in hosting - Why I would NEVER recommend ASPNix
Tip of the Day: Creating a control that displays multiple types of messages using the IValidator interface
Tip of the Day: The evolution of dynamic, case insensitive LINQ to Object search
Tuesday, January 25, 2005 9:28:46 PM (GMT Standard Time, UTC+00:00)
Thanks a million, this saved me today!
Brad Daily
Wednesday, January 26, 2005 1:16:31 AM (GMT Standard Time, UTC+00:00)
Always glad to help!
Daryl
Thursday, February 17, 2005 1:31:33 AM (GMT Standard Time, UTC+00:00)
So this tells you what caused the postback, but is there a way to determine if there are any other events that have also happened (that didn't cause a postback)?
Lance
Thursday, February 17, 2005 2:26:59 AM (GMT Standard Time, UTC+00:00)
Do you mean client side events? Or do you mean a control which fires an event which may bubble?
Daryl
Comments are closed.