| Groups | Blog | Home |
asp.net : ASP.NET 2 Beta 2 JavaScript bad rendering
something like this: this.txtUserName.Attributes.Add("onkeydown","if((event.which && event.which == 13)||(event.keyCode && event.keyCode == 13)){document.Form1.cmdLogin.click();return false;}else return true;"); that code rendered javascript to the client OK. Now that I upgraded to ASP.NET 2 Beta 2 it is rendering && instead of &&, so clients are getting this instead: if((event.which && event.which == 13)||(event.keyCode && event.keyCode == 13)){document.Form1.cmdLogin.click();return false;}else return true; Please HELP!! Thanks, Alejandro Penate-Diaz.
Can you show how you render the script to the client? IOW, do you use Page.ClientScriptRegisterClientScriptBlock
or something else? -Brock DevelopMentor http://staff.develop.com/ballen [quoted text, click to view] > Hi. I was handling key events nicely using some Javascript on my apps > using something like this: > this.txtUserName.Attributes.Add("onkeydown","if((event.which && > event.which == 13)||(event.keyCode && event.keyCode == > 13)){document.Form1.cmdLogin.click();return false;}else return > true;"); > > that code rendered javascript to the client OK. Now that I upgraded to > ASP.NET 2 Beta 2 it is rendering && instead of &&, so clients > are getting this instead: > > if((event.which && event.which == 13)||(event.keyCode > && event.keyCode == > 13)){document.Form1.cmdLogin.click();return false;}else return true; > > Please HELP!! > > Thanks, > > Alejandro Penate-Diaz. >
using something like this in my Page_Load method.:
this.txtUserName.Attributes.Add("onkeydown","if((event.which &&event.which == 13)||(event.keyCode && event.keyCode ==13)){document.Form1.cmdLogin.click();return false;}else return true;"); [quoted text, click to view] "Brock Allen" <ballen@NOSPAMdevelop.com> wrote in message news:790818632525322628083384@msnews.microsoft.com... > Can you show how you render the script to the client? IOW, do you use > Page.ClientScriptRegisterClientScriptBlock or something else? > > -Brock > DevelopMentor > http://staff.develop.com/ballen > > > >> Hi. I was handling key events nicely using some Javascript on my apps >> using something like this: >> this.txtUserName.Attributes.Add("onkeydown","if((event.which && >> event.which == 13)||(event.keyCode && event.keyCode == >> 13)){document.Form1.cmdLogin.click();return false;}else return >> true;"); >> >> that code rendered javascript to the client OK. Now that I upgraded to >> ASP.NET 2 Beta 2 it is rendering && instead of &&, so clients >> are getting this instead: >> >> if((event.which && event.which == 13)||(event.keyCode >> && event.keyCode == >> 13)){document.Form1.cmdLogin.click();return false;}else return true; >> >> Please HELP!! >> >> Thanks, >> >> Alejandro Penate-Diaz. >> > > >
do you think this would work?
<system.web> <!-- other elements here --> <XHTML11Conformance enableObsoleteRendering="true" /> </system.web> [quoted text, click to view] "Brock Allen" <ballen@NOSPAMdevelop.com> wrote in message news:790818632525322628083384@msnews.microsoft.com... > Can you show how you render the script to the client? IOW, do you use > Page.ClientScriptRegisterClientScriptBlock or something else? > > -Brock > DevelopMentor > http://staff.develop.com/ballen > > > >> Hi. I was handling key events nicely using some Javascript on my apps >> using something like this: >> this.txtUserName.Attributes.Add("onkeydown","if((event.which && >> event.which == 13)||(event.keyCode && event.keyCode == >> 13)){document.Form1.cmdLogin.click();return false;}else return >> true;"); >> >> that code rendered javascript to the client OK. Now that I upgraded to >> ASP.NET 2 Beta 2 it is rendering && instead of &&, so clients >> are getting this instead: >> >> if((event.which && event.which == 13)||(event.keyCode >> && event.keyCode == >> 13)){document.Form1.cmdLogin.click();return false;}else return true; >> >> Please HELP!! >> >> Thanks, >> >> Alejandro Penate-Diaz. >> > > >
that didnt work, when I build the app I get an error like:
Error 1 Unrecognized configuration section XHTML11Conformance. c:\inetpub\wwwroot\qman\Web.config 9 [quoted text, click to view] "Brock Allen" <ballen@NOSPAMdevelop.com> wrote in message news:790818632525322628083384@msnews.microsoft.com... > Can you show how you render the script to the client? IOW, do you use > Page.ClientScriptRegisterClientScriptBlock or something else? > > -Brock > DevelopMentor > http://staff.develop.com/ballen > > > >> Hi. I was handling key events nicely using some Javascript on my apps >> using something like this: >> this.txtUserName.Attributes.Add("onkeydown","if((event.which && >> event.which == 13)||(event.keyCode && event.keyCode == >> 13)){document.Form1.cmdLogin.click();return false;}else return >> true;"); >> >> that code rendered javascript to the client OK. Now that I upgraded to >> ASP.NET 2 Beta 2 it is rendering && instead of &&, so clients >> are getting this instead: >> >> if((event.which && event.which == 13)||(event.keyCode >> && event.keyCode == >> 13)){document.Form1.cmdLogin.click();return false;}else return true; >> >> Please HELP!! >> >> Thanks, >> >> Alejandro Penate-Diaz. >> > > >
Well, I see the & that it's rendering, but the code executes properly.
Does your javascript work? -Brock DevelopMentor http://staff.develop.com/ballen [quoted text, click to view] > using something like this in my Page_Load method.: > > this.txtUserName.Attributes.Add("onkeydown","if((event.which > &&event.which == 13)||(event.keyCode && event.keyCode > ==13)){document.Form1.cmdLogin.click();return false;}else return > true;"); > > "Brock Allen" <ballen@NOSPAMdevelop.com> wrote in message > news:790818632525322628083384@msnews.microsoft.com... > >> Can you show how you render the script to the client? IOW, do you use >> Page.ClientScriptRegisterClientScriptBlock or something else? >> >> -Brock >> DevelopMentor >> http://staff.develop.com/ballen >>> Hi. I was handling key events nicely using some Javascript on my >>> apps using something like this: >>> this.txtUserName.Attributes.Add("onkeydown","if((event.which && >>> event.which == 13)||(event.keyCode && event.keyCode == >>> 13)){document.Form1.cmdLogin.click();return false;}else return >>> true;"); >>> >>> that code rendered javascript to the client OK. Now that I upgraded >>> to ASP.NET 2 Beta 2 it is rendering && instead of &&, so >>> clients are getting this instead: >>> >>> if((event.which && event.which == 13)||(event.keyCode >>> && event.keyCode == >>> 13)){document.Form1.cmdLogin.click();return false;}else return true; >>> >>> Please HELP!! >>> >>> Thanks, >>> >>> Alejandro Penate-Diaz. >>>
It doesn't work
[quoted text, click to view] "Brock Allen" <ballen@NOSPAMdevelop.com> wrote in message news:811760632527066521246944@msnews.microsoft.com... > Well, I see the & that it's rendering, but the code executes properly. > Does your javascript work? > > -Brock > DevelopMentor > http://staff.develop.com/ballen > > > >> using something like this in my Page_Load method.: >> >> this.txtUserName.Attributes.Add("onkeydown","if((event.which >> &&event.which == 13)||(event.keyCode && event.keyCode >> ==13)){document.Form1.cmdLogin.click();return false;}else return >> true;"); >> >> "Brock Allen" <ballen@NOSPAMdevelop.com> wrote in message >> news:790818632525322628083384@msnews.microsoft.com... >> >>> Can you show how you render the script to the client? IOW, do you use >>> Page.ClientScriptRegisterClientScriptBlock or something else? >>> >>> -Brock >>> DevelopMentor >>> http://staff.develop.com/ballen >>>> Hi. I was handling key events nicely using some Javascript on my >>>> apps using something like this: >>>> this.txtUserName.Attributes.Add("onkeydown","if((event.which && >>>> event.which == 13)||(event.keyCode && event.keyCode == >>>> 13)){document.Form1.cmdLogin.click();return false;}else return >>>> true;"); >>>> >>>> that code rendered javascript to the client OK. Now that I upgraded >>>> to ASP.NET 2 Beta 2 it is rendering && instead of &&, so >>>> clients are getting this instead: >>>> >>>> if((event.which && event.which == 13)||(event.keyCode >>>> && event.keyCode == >>>> 13)){document.Form1.cmdLogin.click();return false;}else return true; >>>> >>>> Please HELP!! >>>> >>>> Thanks, >>>> >>>> Alejandro Penate-Diaz. >>>> > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |