C# ASP.NET : How to add javascript dynamically? | Tech Off

turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein

This thing won't do anything... any idéa why?

protected void Page_Load(object sender, EventArgs e)
{
ClientScriptManager CS = this.ClientScript;
StringBuilder SB = new StringBuilder();
SB.Append("window.alert(\"1111\");");
CS.RegisterClientScriptBlock(this.GetType(), "MyScript", SB.ToString(), true);
}

Edit : The script wont' even show if I do "View source", I even tried RegisterStartupScript.

Thanks!

W3bbo
The Master of Baiters

Try this example taken from MSDN (not that I disapprove of the ClientScriptManager API)

( ms-help://MS.VSCC.v90/MS.MSDNQTR.v90.en/fxref_system.web/html/2f72329c-2263-9feb-11b6-b3fa14498b7b.htm )

<%@ Page Language="C#"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<script runat="server">
  public void Page_Load(Object sender, EventArgs e)
  {
    // Define the name and type of the client scripts on the page.
    String csname1 = "PopupScript";
    String csname2 = "ButtonClickScript";
    Type cstype = this.GetType();

    // Get a ClientScriptManager reference from the Page class.
    ClientScriptManager cs = Page.ClientScript;

    // Check to see if the startup script is already registered.
    if (!cs.IsStartupScriptRegistered(cstype, csname1))
    {
      String cstext1 = "alert('Hello World');";
      cs.RegisterStartupScript(cstype, csname1, cstext1, true);
    }

    // Check to see if the client script is already registered.
    if (!cs.IsClientScriptBlockRegistered(cstype, csname2))
    {
      StringBuilder cstext2 = new StringBuilder();
      cstext2.Append("<script type=\"text/javascript\"> function DoClick() {");
      cstext2.Append("Form1.Message.value='Text from client script.'} </");
      cstext2.Append("script>");
      cs.RegisterClientScriptBlock(cstype, csname2, cstext2.ToString(), false);
    }
  }
</script>
<html xmlns="http://www.w3.org/1999/xhtml" >
  <head>
    <title>ClientScriptManager Example</title>
  </head>
  <body>
     <form id="Form1"
         runat="server">
        <input type="text" id="Message" /> <input type="button" value="ClickMe" onclick="DoClick()" />
     </form>
  </body>
</html>

turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein

In reply to W3bbo

#Aug 9th @ 2:21 PM

Thanks, weird... it seems that my script works too but I need to have "<form id="form_TT" runat="server"></form>" or it won't run for some reason.

turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein

In reply to turrican

#Aug 9th @ 2:43 PM

aaaaaargh... <form id="form_TT" runat="server"></form> adds a "name" attrib and it in turns make my code invalidated in w3c validator ( 1.0 strict ).... !"#¤@£$@...

W3bbo
The Master of Baiters

In reply to turrican

#Aug 9th @ 2:50 PM

Did you set <xhtmlConformance mode="Strict" /> in Web.config?

Note that ASP.NET does not recognise the W3C Validator's UA string and will automatically revert to Transitional Conformance regardless of the <xhtmlConformance /> configuration element. You'll need an overarching default.browser file to override it all.

turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein

In reply to W3bbo

#Aug 9th @ 3:46 PM

I added

<system.web>
<xhtmlConformance mode="Strict" />
</system.web>

Now the form is ok but <input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" <----- gives me a "name"

Not sure what you mean by "You'll need an overarching default.browser file to override it all." *confused*

W3bbo
The Master of Baiters

In reply to turrican

#Aug 9th @ 3:59 PM

The name="" attribute for <input />, <textarea>, and <select> elements isn't just allowed, it's actually required to give name/value pair results. The name="" attribute is only bad if it's used as id="". ASP.NET is doing it right.

As for .browser files:

ASP.NET (stupidly, some might say) uses a whitelist browser caps ("capabilities") system to determine what capabilities (Java, Flash, ECMAScript support, maximum supported DOM level, etc) the current UA supports by matching the User-Agent string against a database of .browser files located in the filesystem. Each .browser file contains the listing of capabilities in an XML format.

.browser files have been around since the days of "classic" ASP (they were in .ini format rather than XML though), so they're nothing new.

ASP.NET first tries the file "default.browser" and if the regular expression or wildcard contained within matches the current UA then it uses that. The .browser file tells ASP.NET how it should render content in ways that cannot be defined in web.config. I've created my own default.browser file that makes ASP.NET assume that every UA (including the W3C Validator) supports everything IE6 does (which in this day and age... does).

Here it is:

<browsers>
	<browser refID="Default">
		<capture></capture>
		<capabilities>
			<capability name="css1"                                        value="true" />
			<capability name="css2"                                        value="true" />
			<capability name="ecmascriptversion"                           value="3.0" />
			<capability name="frames"                                      value="true" />
			<capability name="inputType"                                   value="keyboard" />
			<capability name="isColor"                                     value="true" />
			<capability name="javaapplets"                                 value="true" />
			<capability name="javascript"                                  value="true" />
			<capability name="jscriptversion"                              value="5.7" />
			<capability name="preferredRenderingType"                      value="xhtml" />
			<capability name="screenBitDepth"                              value="32" />
			<capability name="supportsAccesskeyAttribute"                  value="true" />
			<capability name="supportsBold"                                value="true" />
			<capability name="supportsCss"                                 value="true" />
			<capability name="supportsDivNoWrap"                           value="true" />
			<capability name="supportsFileUpload"                          value="true" />
			<capability name="supportsFontName"                            value="true" />
			<capability name="supportsFontSize"                            value="true" />
			<capability name="supportsImageSubmit"                         value="true" />
			<capability name="supportsItalic"                              value="true" />
			<capability name="supportsMaintainScrollPositionOnPostback"    value="true" />
			<capability name="supportsMultilineTextBoxDisplay"             value="true" />
			<capability name="supportsVCard"                               value="true" />
			<capability name="supportXmlHttp"                              value="true" />
			<capability name="tables"                                      value="true" />
			<!-- Don't use XhtmlTextWriter since <form> renders without the <div> wrapper around the hidden inputs -->
			<capability name="tagwriter"                                   value="System.Web.UI.HtmlTextWriter" />
			<capability name="w3cdomversion"                               value="2.0" />
			<capability name="xml"                                         value="true" />
		</capabilities>
		
		<controlAdapters markupTextWriterType="System.Web.UI.HtmlTextWriter">
			
		</controlAdapters>
	</browser>
</browsers>

stevo_
Casablanca != Manchester

In reply to turrican

#Aug 9th @ 3:59 PM

Pretty sure that in xhtml 1.0, some browsers require the name attribute on form fields, they don't always use the id attribute.. to say this is your first asp.net application (I'm assuming since all the questions), its really nuts to be aiming for an xhtml 1.0 strict compilation.. you may well think that you should learn the best first.. but as far as xhtml strict goes right now.. the browser support just isn't good.. you put lots of restrictions on yourself where the replaced functionality just isn't well supported..

turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein

In reply to stevo_

#Aug 9th @ 4:15 PM

Not true. The website I'm writing is pretty complex and it looks 100% alike in Safari, Opera, IE7, FireFox... what more can I ask for?

Smiley

turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein

In reply to W3bbo

#Aug 9th @ 4:09 PM

Excellent, thank you!

turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein

In reply to W3bbo

#Aug 9th @ 4:09 PM

Ok, I feel really dumb right now, I used your default.browser, it still gives me "name" when validating, so it fails :

Line 29, Column 15: there is no attribute "name".
<form name= ...

Sad

JChung2006

In reply to turrican

#Aug 9th @ 4:30 PM

Turn on Strict XHTML conformance in your Web.config again:

<configuration>
  <system.web> 
    <xhtmlConformance mode="Strict"/>
  </system.web>
</configuration>

What's the problem with the name attribute for your INPUT elements? While the name attribute may be deprecated, it is still valid XHTML.

turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein

In reply to JChung2006

#Aug 9th @ 6:38 PM

I have <xhtmlConformance mode="Strict"/> in my web.config. The INPUT gets a "Name" so w3c validator won't validate the site. I don't know what to do ;(

Edit : I got :

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein

In reply to JChung2006

#Aug 9th @ 6:38 PM

I got :

When I "run" it, it gives :

</form>

Basically, I want to run "DoGrass();" dynamically. Which won't work unless I got a

... but when I add it, it creates a <INPUT... with a "NAME" tag in it, which in returns prevents my site to get validated.

So so so confusing. :O
</form>

turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein

In reply to JChung2006

#Aug 9th @ 6:38 PM

This is what I found so far : http://www.liquid-internet.co.uk/content/dynamic/pages/series1article1.aspx

Creates some sort of customform and prevent .NET to add the "NAME" tag in order to validate it for STRICT. It seems way too much work so I think I'll have to dump strict for transitional for now.

But... this SUCKS.

turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein

In reply to W3bbo

#Aug 9th @ 4:09 PM

Using a custom "ResponseFilter", I managed to parse out name="__VIEWSTATE" , but it feels rather slow to do this. So I'll have to use transitional I guess.

stevo_
Casablanca != Manchester

In reply to turrican

#Aug 9th @ 11:04 PM

Aw how cute, you think all the difference is the looks? plus now you've already fallen back to transitional.. wow, didn't take long.

W3bbo
The Master of Baiters

In reply to stevo_

#Aug 10th @ 3:25 AM

Epic Fail.

Turrican:

Please, listen to me: you're doing it wrong.

The name="" attribute is valid in XHTML1.0 Strict and XHTML1.1 for <input />, <textarea>, and <select>. It is a required attribute of those elements to get forms to work in the first place. Check the specification if you don't believe me.

Do not confuse it with the name="" attribute on the <form> element, which ASP.NET only serves up if you have <xhtmlConformance mode="" /> not set to "Strict" or you haven't overriden the Browser definitions.

turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein

In reply to W3bbo

#Aug 10th @ 3:57 AM

I undrestand. Well, with your help I got rid of "name" tag in the <form>, the input has "name" and as you suggest it's valid 1.0 strict. However, the darn w3c validator won't validate it! I have been up all night trying to figure this thing out, I'm about to drop dead I think.

Sad

turrican
Condemnation without investigation is the height of ignorance! - Albert Einstein

In reply to W3bbo

#Aug 10th @ 3:57 AM

I did it! Finally :

I added a .browser file containing this :

blowdart
Peek-a-boo

In reply to turrican

#Aug 10th @ 4:30 AM