[thelist] IE Field Tip

Jeff Howden jeff at jeffhowden.com
Thu Jul 17 01:53:42 CDT 2003


joshua,

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: Joshua Olson
>
> So it seems that your statement about preferring onblur
> over onpropertychange has more to do with poor
> programming than it does about one method being better
> than another?
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

no, it stems from the fact that using the onblur event handler is poor
programming.  i personally can't think of a practical use for the onblur
event handler, except on form fields that don't support the onchange event
handler.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> That being said, I think I'll stick with onblur, since
> it (hopefully) has universal support whereas
> onpropertychange probably does not.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

obviously you've been missing the point i've been trying to make.

first, use onchange to fire the javascript you need to run when the value
changes.

second, use onpropertychange to fire the same javascript you need to run
when the value changes as a result of using autocomplete.  the fact that
browsers other than win/ie don't support onpropertychange is moot since no
other browser implements autocomplete such that the onpropertychange event
handler is necessary.  in other words, who cares whether onpropertychange is
universally supported or not, because you're using it to address an issue
only with the browser that supports autocomplete.

.jeff

——————————————————————————————————————————————————————
Jeff Howden - Web Application Specialist
Résumé - http://jeffhowden.com/about/resume/
Code Library - http://evolt.jeffhowden.com/jeff/code/




More information about the thelist mailing list