J
jake
I could not find any specific discussion on this, so please bear with
me as I am less experienced programming for the web than I am for the
desktop.
I have a master page with a <body> tag such as this (as this is part
of the default content from the horse's mouth);
<body>
<form id="form1" runat="server">
<div>
<asp:ContentPlaceHolder ID="ContentPlaceHolder1"
runat="server">
</asp:ContentPlaceHolder>
</div>
</form>
</body>
This MasterPage serves about 30 pages. Many of the pages have a
submit button which promotes a submit behavior in the displayed page.
I need a few of the "other" pages that share the same MasterPage to
each have a separate onsubmit event handler without having a submit
button. Seeing as to the fact that the ContentPlaceHolder is inside
the <form> tag, I can't simply put an onsubmit="handler()" in the
<form> tag lest I intend it to affect all the pages that share this
MasterPage.
How can I do this without changing the existing setup and potentially
damaging the hundreds of thousands of lines of code that are already
written.
Now, I can, of course, kludge it and bend it to suit my needs, but is
there an elegant way?
Thanks,
jake
me as I am less experienced programming for the web than I am for the
desktop.
I have a master page with a <body> tag such as this (as this is part
of the default content from the horse's mouth);
<body>
<form id="form1" runat="server">
<div>
<asp:ContentPlaceHolder ID="ContentPlaceHolder1"
runat="server">
</asp:ContentPlaceHolder>
</div>
</form>
</body>
This MasterPage serves about 30 pages. Many of the pages have a
submit button which promotes a submit behavior in the displayed page.
I need a few of the "other" pages that share the same MasterPage to
each have a separate onsubmit event handler without having a submit
button. Seeing as to the fact that the ContentPlaceHolder is inside
the <form> tag, I can't simply put an onsubmit="handler()" in the
<form> tag lest I intend it to affect all the pages that share this
MasterPage.
How can I do this without changing the existing setup and potentially
damaging the hundreds of thousands of lines of code that are already
written.
Now, I can, of course, kludge it and bend it to suit my needs, but is
there an elegant way?
Thanks,
jake