Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!news-1.dfn.de!news.dfn.de!news.informatik.hu-berlin.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Mel Smith" Newsgroups: comp.lang.javascript Subject: Re: Debugging Errors -- a conundrum -- I think Date: Mon, 20 Jan 2014 15:33:52 -0700 Lines: 29 Message-ID: References: <52dd55dd$0$6554$9b4e6d93@newsspool4.arcor-online.net> <52dd809b$0$6547$9b4e6d93@newsspool4.arcor-online.net> <52dd8824$0$6563$9b4e6d93@newsspool4.arcor-online.net> X-Trace: individual.net hpKbF3/qu2ZGOk3Zc6PsfAnjVolZZOuhfbsEI38/5CQaGhxNLK Cancel-Lock: sha1:ne67ovd6wuHS5a/hEl/4qWTLt6M= X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-RFC2646: Format=Flowed; Original Xref: csiph.com comp.lang.javascript:22731 Christoph said: > Now I've read your OP again: > >> btw, the 'suspected place' is a function that is called by 'onclick' > > on an option in a tag > > I suggest you don't use the onclick/onchange attribute of the option > elements, but instead use the onchange attribute of the select element. > How to access the selected option is explained in the FAQ section "How > do I get the value of a form control?"[1]. AISB, I was getting errors (a week ago) using the onchange event. Then, (after googling 'IE8 and onchange problems'), I noted several search results that indicated onchange should be replaced with onclick. So, now I'm totally confused -- but at least I've got console.log to work -- with no helpful results. I still get the 'hang' -- but with an alert() planted in the onclick function everything's fine in IE. Thanks all. -Mel