Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #22731

Re: Debugging Errors -- a conundrum -- I think

From "Mel Smith" <med_cutout_syntel@aol.com>
Newsgroups comp.lang.javascript
Subject Re: Debugging Errors -- a conundrum -- I think
Date 2014-01-20 15:33 -0700
Message-ID <bk5mijF7pdgU1@mid.individual.net> (permalink)
References (2 earlier) <bk55meF44sjU1@mid.individual.net> <bk5d0fF5n94U1@mid.individual.net> <52dd809b$0$6547$9b4e6d93@newsspool4.arcor-online.net> <bk5es2F645gU1@mid.individual.net> <52dd8824$0$6563$9b4e6d93@newsspool4.arcor-online.net>

Show all headers | View raw


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 <select> element.

    No, the 'onclick' function is in the <select> 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

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Debugging Errors -- a conundrum -- I think "Mel Smith" <med_cutout_syntel@aol.com> - 2014-01-20 09:48 -0700
  Re: Debugging Errors -- a conundrum -- I think Christoph Michael Becker <cmbecker69@arcor.de> - 2014-01-20 17:59 +0100
    Re: Debugging Errors -- a conundrum -- I think "Mel Smith" <med_cutout_syntel@aol.com> - 2014-01-20 10:45 -0700
      Re: Debugging Errors -- a conundrum -- I think "Mel Smith" <med_cutout_syntel@aol.com> - 2014-01-20 12:50 -0700
        Re: Debugging Errors -- a conundrum -- I think Christoph Michael Becker <cmbecker69@arcor.de> - 2014-01-20 21:01 +0100
          Re: Debugging Errors -- a conundrum -- I think "Mel Smith" <med_cutout_syntel@aol.com> - 2014-01-20 13:22 -0700
            Re: Debugging Errors -- a conundrum -- I think Christoph Michael Becker <cmbecker69@arcor.de> - 2014-01-20 21:33 +0100
              Re: Debugging Errors -- a conundrum -- I think Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-01-20 21:42 +0100
              Re: Debugging Errors -- a conundrum -- I think "Mel Smith" <med_cutout_syntel@aol.com> - 2014-01-20 15:33 -0700
                Re: Debugging Errors -- a conundrum -- I think "Mel Smith" <med_cutout_syntel@aol.com> - 2014-01-20 16:02 -0700
                Re: Debugging Errors -- a conundrum -- I think Christoph Michael Becker <cmbecker69@arcor.de> - 2014-01-21 00:28 +0100
                Re: Debugging Errors -- a conundrum -- I think Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-01-21 06:01 +0100
                Re: Debugging Errors -- a conundrum -- I think "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-01-21 08:47 +0100
                Re: Debugging Errors -- a conundrum -- I think Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-01-21 13:01 +0100
                Re: Debugging Errors -- a conundrum -- I think John Harris <niam@jghnorth.org.uk.invalid> - 2014-01-22 15:18 +0000
                Re: Debugging Errors -- a conundrum -- I think Norman Peelman <npeelman@cfl.rr.com> - 2014-01-21 06:13 -0500
                Re: Debugging Errors -- a conundrum -- I think "Mel Smith" <med_cutout_syntel@aol.com> - 2014-01-21 10:01 -0700
          Re: Debugging Errors -- a conundrum -- I think Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-01-20 21:37 +0100

csiph-web