Comments on: Degradable SELECT onChange http://davidwalsh.name/select-onchange Legendary scribbles about JavaScript, HTML5, AJAX, PHP, CSS, and ∞. Thu, 09 Feb 2012 02:40:12 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Zachttp://davidwalsh.name/select-onchange/comment-page-1#comment-10685 Zac Sat, 25 Jul 2009 20:10:51 +0000 http://davidwalsh.name/?p=3173#comment-10685 David, I just want to say that your blog rocks. David, I just want to say that your blog rocks.

]]> By: Adriaanhttp://davidwalsh.name/select-onchange/comment-page-1#comment-10684 Adriaan Sat, 25 Jul 2009 17:55:41 +0000 http://davidwalsh.name/?p=3173#comment-10684 @Stephen: because this is framework independent javascript @Stephen: because this is framework independent javascript

]]> By: Stephenhttp://davidwalsh.name/select-onchange/comment-page-1#comment-10683 Stephen Sat, 25 Jul 2009 17:45:07 +0000 http://davidwalsh.name/?p=3173#comment-10683 Am I missing something or why do you use getElementById() instead of $()? Am I missing something or why do you use getElementById() instead of $()?

]]> By: Peter Velichkovhttp://davidwalsh.name/select-onchange/comment-page-1#comment-10669 Peter Velichkov Fri, 24 Jul 2009 22:20:35 +0000 http://davidwalsh.name/?p=3173#comment-10669 why don't you just move the script bellow the form, this way you are sure you can access the element and don't have to wait for onLoad why don’t you just move the script bellow the form, this way you are sure you can access the element and don’t have to wait for onLoad

]]> By: Jameshttp://davidwalsh.name/select-onchange/comment-page-1#comment-10622 James Thu, 23 Jul 2009 22:36:07 +0000 http://davidwalsh.name/?p=3173#comment-10622 @Adriaan, only browsers that comply with the W3C event model support "addEventListener" - IE uses "attachEvent". btw, @David, IE doesn't support event capturing in the same way as other browsers so the third argument ("false") can be removed from "select.attachEvent('onchange',handler,false);" @Adriaan, only browsers that comply with the W3C event model support “addEventListener” – IE uses “attachEvent”. btw, @David, IE doesn’t support event capturing in the same way as other browsers so the third argument (“false”) can be removed from “select.attachEvent(‘onchange’,handler,false);”

]]> By: Adriaanhttp://davidwalsh.name/select-onchange/comment-page-1#comment-10619 Adriaan Thu, 23 Jul 2009 18:11:38 +0000 http://davidwalsh.name/?p=3173#comment-10619 Might I ask why you are doing this:<blockquote> if(select.addEventListener){ </blockquote>don't all browsers support it or what? Might I ask why you are doing this:

if(select.addEventListener){

don’t all browsers support it or what?

]]> By: David Walshhttp://davidwalsh.name/select-onchange/comment-page-1#comment-10617 David Walsh Thu, 23 Jul 2009 16:57:03 +0000 http://davidwalsh.name/?p=3173#comment-10617 <p>Hmmm, given more though, I could simply put the <script> tag into the body tag and not wait for the load event.</p> Hmmm, given more though, I could simply put the

]]> By: David Walshhttp://davidwalsh.name/select-onchange/comment-page-1#comment-10615 David Walsh Thu, 23 Jul 2009 15:10:18 +0000 http://davidwalsh.name/?p=3173#comment-10615 <p>@James: My goal was to avoid using a JS lib. I suppose it would be possible to implement a lib-independent DOMREADY function.</p> @James: My goal was to avoid using a JS lib. I suppose it would be possible to implement a lib-independent DOMREADY function.

]]> By: Jameshttp://davidwalsh.name/select-onchange/comment-page-1#comment-10614 James Thu, 23 Jul 2009 15:08:14 +0000 http://davidwalsh.name/?p=3173#comment-10614 Using the "onLoad" event is a bad idea; there'll be a significant amount of time between the button being visible and it being removed; this flicker isn't exactly good for the user experience. It's better to remove it the button as soon as the element exists - you could do this by using one of the psuedo-domReady events present in many of today's libraries. Using the “onLoad” event is a bad idea; there’ll be a significant amount of time between the button being visible and it being removed; this flicker isn’t exactly good for the user experience. It’s better to remove it the button as soon as the element exists – you could do this by using one of the psuedo-domReady events present in many of today’s libraries.

]]> By: Jeremy Parrishhttp://davidwalsh.name/select-onchange/comment-page-1#comment-10613 Jeremy Parrish Thu, 23 Jul 2009 14:41:21 +0000 http://davidwalsh.name/?p=3173#comment-10613 Even though it is possible to do it this way, I would much rather just wrap the submit button in a noscript tag. Maybe it's just me, but I think it's a bit tacky when I see stuff show briefly while loading and then disappear. Are there any issues with using a noscript tag? Even though it is possible to do it this way, I would much rather just wrap the submit button in a noscript tag. Maybe it’s just me, but I think it’s a bit tacky when I see stuff show briefly while loading and then disappear. Are there any issues with using a noscript tag?

]]>