C
C. Levasseur
I would like to use client side scripting for enabling/disabling buttons
(depending on values in other fields). This worked fine in Asp.Net 1.1 but
in Asp.Net 2.0, all the names and the id's of the web and html controls are
modified, for example:
<asp:Button Runat="server" ID="modifyCtrl" Text="Modify" /asp:Button> is
generated as
<input type="submit" name="ctl00$main$modifyCtrl" value="Modify"
id="ctl00_main_modifyCtrl" />
How can my client side scripts disable my button if Asp.Net 2.0 modifies the
ID's and the names? Is there a method I can call that will convert my client
scripts so they won't break if Asp.Net changes the naming convention in a
future version (such as RegisterClientScriptBlock() )?
C.Levasseur
(depending on values in other fields). This worked fine in Asp.Net 1.1 but
in Asp.Net 2.0, all the names and the id's of the web and html controls are
modified, for example:
<asp:Button Runat="server" ID="modifyCtrl" Text="Modify" /asp:Button> is
generated as
<input type="submit" name="ctl00$main$modifyCtrl" value="Modify"
id="ctl00_main_modifyCtrl" />
How can my client side scripts disable my button if Asp.Net 2.0 modifies the
ID's and the names? Is there a method I can call that will convert my client
scripts so they won't break if Asp.Net changes the naming convention in a
future version (such as RegisterClientScriptBlock() )?
C.Levasseur