G
Gregory Gadow
I have a large website written to use ASP.Net 2.0. The master page has a
"logout" button. If the child page does not have an explicitly defined
default button (most do not), the page posts back with the logout button
as the default, throwing the user out of the system.
I can supress all postbacks by putting "onsubmit='return false'" in the
form tag of the master page. That, however, renders all button clicks
and other postback calls non-functional. Is there a way in ASP.Net 2.0
to supress the concept of a default button entirely but still leave
buttons functional?
"logout" button. If the child page does not have an explicitly defined
default button (most do not), the page posts back with the logout button
as the default, throwing the user out of the system.
I can supress all postbacks by putting "onsubmit='return false'" in the
form tag of the master page. That, however, renders all button clicks
and other postback calls non-functional. Is there a way in ASP.Net 2.0
to supress the concept of a default button entirely but still leave
buttons functional?