ansaurus

Question

Answer 1

+2 A:

Your script probably stops because there is no hidden value anywhere.

You also have an extra } at the end of the script.

This should work:

function ClearValue() {
   var txtName = document.getElementById('<%=txtName.ClientID %>');
   txtName.className = '';
   txtName.className = 'TextBox2';
}

Thought this will also work well in modern browsers (though broken in older versions of IE, thanks @David Dorward):

function ClearValue() {
   var txtName = document.getElementById('<%=txtName.ClientID %>');
   txtName.setAttribute('class', '');
   txtName.setAttribute('class', 'TextBox2');
}

You really should try using jQuery which makes this kind of thing a doddle:

function ClearValue()
{
   $('<%=txtName.ClientID %>').toggleClass('TextBox2');
}

Oded 2010-10-03 19:06:34

Using `setAttribute` will not work well. It is broken in older versions of IE.

David Dorward 2010-10-03 19:21:17

@David Dorward - thanks for the correction. Answer updated.

Oded 2010-10-03 19:23:20

Can the downvote please explain?

Oded 2010-10-03 19:30:22

@oded: jQuery=bad, especially when having to debug one of the many current bugs. Then your version is automatically different from the hosted version. Then when they make a new feature and don't patch your previous issue...horribad. As you said the problem is probably because of the extra `}` or `hidden.value`. The lack of `;` also could be causing problems.

vol7ron 2010-10-03 19:32:20

@vol7ron - Are you suggesting that jQuery is badly broken and should never be used? Can you back this up?

Oded 2010-10-03 19:34:26

I'm saying that if you do anything advanced, you'll come across bugs... many bugs - recently, I was doing something simple with a JS slideshow that worked in everything except IE8. The only solution I had was to fix it myself and the moment you have to go into the code and fix it, it takes away the major advantage of the package, which, in my opinion is the caching. -- While everyone is pushing jQuery, the real solution, IMHO, is to further the development of ECMAScript itself. Having something with less overhead, native to browsers, that takes less code is the best hope.

vol7ron 2010-10-03 23:46:24

While I say this, the simplicities of the language don't have problems, but why use it if you're doing something simple? it may be likely that I adopt `jQuery` in the future; but as for now, I'm still waiting for it to evolve just a little bit more. Until that happens, I'll probably remain re-inventing the wheel, which I'm not ashamed of, as I rather know what it takes to do/make/modify something, than be handed it w/o knowing the intricacies.

vol7ron 2010-10-03 23:49:29

Answer 2

A:

try with

txtName.setAttribute("class",'TextBox2);

frisco 2010-10-03 19:06:58

The `className` property (used in the original question) is better supported than `setAttribute`

David Dorward 2010-10-03 19:20:40

Answer 3

A:

             txtname.setAttribute("className", newClass); //For IE; harmless to other browsers.

From http://www.webdeveloper.com/forum/showthread.php?t=134282

Hulk 2010-10-03 19:07:22

Using the `className` property (as the original question already does) instead of the `setAttribute` method avoids the need to hack older versions of IE in this way.

David Dorward 2010-10-03 19:20:09

ansaurus

tags:

views:

answers:

change css using javscript

related questions