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

Groups > comp.lang.javascript > #25682 > unrolled thread

Onclick event doesnt work in webkit browser

Back to article view | Back to comp.lang.javascript

Contents

  Onclick event doesnt work in webkit browser PS <poonam.sachdeva5@gmail.com> - 2014-08-15 14:44 -0700
    Re: Onclick event doesnt work in webkit browser "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-08-16 00:15 +0200
      Re: Onclick event doesnt work in webkit browser PS <poonam.sachdeva5@gmail.com> - 2014-08-15 15:22 -0700
        Re: Onclick event doesnt work in webkit browser "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-08-16 00:40 +0200
          Re: Onclick event doesnt work in webkit browser PS <poonam.sachdeva5@gmail.com> - 2014-08-15 15:43 -0700
            Re: Onclick event doesnt work in webkit browser PS <poonam.sachdeva5@gmail.com> - 2014-08-15 15:55 -0700
              Re: Onclick event doesnt work in webkit browser "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-08-16 10:09 +0200
            Re: Onclick event doesnt work in webkit browser "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-08-16 10:04 +0200
            Re: Onclick event doesnt work in webkit browser Tim Streater <timstreater@greenbee.net> - 2014-08-16 09:55 +0100
      Re: Onclick event doesnt work in webkit browser "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-16 01:21 +0200
        Re: Onclick event doesnt work in webkit browser PS <poonam.sachdeva5@gmail.com> - 2014-08-15 16:37 -0700
          Re: Onclick event doesnt work in webkit browser "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-16 02:09 +0200
            Re: Onclick event doesnt work in webkit browser John Harris <niam@jghnorth.org.uk.invalid> - 2014-08-16 17:24 +0100
              Re: Onclick event doesnt work in webkit browser "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-16 18:37 +0200
                FAQ (was: Onclick event doesnt work in webkit browser) Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-08-16 20:19 +0200
                  Re: FAQ (was: Onclick event doesnt work in webkit browser) John Harris <niam@jghnorth.org.uk.invalid> - 2014-08-17 18:10 +0100
                    Re: FAQ (was: Onclick event doesnt work in webkit browser) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-08-17 19:28 +0200
                      Re: FAQ (was: Onclick event doesnt work in webkit browser) John Harris <niam@jghnorth.org.uk.invalid> - 2014-08-18 14:44 +0100
                        Re: FAQ (was: Onclick event doesnt work in webkit browser) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-08-18 22:46 +0200
                    Re: FAQ "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-17 21:31 +0200
                      Re: FAQ John Harris <niam@jghnorth.org.uk.invalid> - 2014-08-18 15:05 +0100
                        Re: FAQ "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-18 22:38 +0200
                          Re: FAQ John Harris <niam@jghnorth.org.uk.invalid> - 2014-08-19 16:23 +0100
                            Re: FAQ "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-21 00:54 +0200
                          Re: FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-08-25 21:01 +0200
                            Re: FAQ "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-09-02 23:07 +0200
                              Re: FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-09-03 01:53 +0200
                                Re: FAQ "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-09-04 02:15 +0200
    Re: Onclick event doesnt work in webkit browser "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-16 01:17 +0200

Page 1 of 2  [1] 2  Next page →

#25682 — Onclick event doesnt work in webkit browser

I am trying to change my GUI on onclick. It works fine in google chrome and firefox but doesnt work in webkit browser. Tried to debug but it doesnt go into the function only. Have tried using addEventListeners but it doesnt work as well. it doesnt trigger the onclick.

<select name="MetricType" id="MetricType" onclick="UpdateMetricFromGUI();">
     <option value=CDatHT >CD</option>
    <option value=HT >HT</option>
   <option value=BowCD >BowCD</option>
    <option value=NeckCD >NeckCD</option>
 </select>


 function UpdateMetricFromGUI() {
        if (m_oSetup === null) {
            msgBox("Please create a recipe first.");
        }
        else if (m_oSetup.Metrics !== null && m_oSetup.Metrics.length > 0) {

            var l_oMetric = m_oSetup.Metrics[m_iCurrentMetricIndex];

            l_oMetric.Category = document.getElementById("MetricType").value;
            l_oMetric.PitchSampling = document.getElementById('ZoneSampling').selectedIndex + 1;      
            UpdateBoxesFromSetup(m_oSetup);
        }
    }

[toc] | [next] | [standalone]

#25683

PS <poonam.sachdeva5@gmail.com> wrote on 15 aug 2014 in
comp.lang.javascript: 

> I am trying to change my GUI on onclick. It works fine in google chrome
> and firefox but doesnt work in webkit browser. Tried to debug but it
> doesnt go into the function only.  

Is Chrome not a webkit browser?

> Have tried using addEventListeners but
> it doesnt work as well. it doesnt trigger the onclick.

Try:

object.onclick = function(){alert(this.value);};

> <select name="MetricType" id="MetricType"
> onclick="UpdateMetricFromGUI();"> 
>      <option value=CDatHT >CD</option>
>     <option value=HT >HT</option>
>    <option value=BowCD >BowCD</option>
>     <option value=NeckCD >NeckCD</option>
>  </select>

Why not go back to the bare code when asking a Q?
The extra code you showed only complicates the issue.

Try:

<select onclick='alert(this.value);'>
  <option value='1 selected' >One</option>
  <option value='2 selected' >Two</option>
</select>



-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#25684

Doesnt work in webkit.
Works in FF.

On Friday, August 15, 2014 3:15:33 PM UTC-7, Evertjan. wrote:
> PS <poonam.sachdeva5@gmail.com> wrote on 15 aug 2014 in
> 
> comp.lang.javascript: 
> 
> 
> 
> > I am trying to change my GUI on onclick. It works fine in google chrome
> 
> > and firefox but doesnt work in webkit browser. Tried to debug but it
> 
> > doesnt go into the function only.  
> 
> 
> 
> Is Chrome not a webkit browser?
> 
> 
> 
> > Have tried using addEventListeners but
> 
> > it doesnt work as well. it doesnt trigger the onclick.
> 
> 
> 
> Try:
> 
> 
> 
> object.onclick = function(){alert(this.value);};
> 
> 
> 
> > <select name="MetricType" id="MetricType"
> 
> > onclick="UpdateMetricFromGUI();"> 
> 
> >      <option value=CDatHT >CD</option>
> 
> >     <option value=HT >HT</option>
> 
> >    <option value=BowCD >BowCD</option>
> 
> >     <option value=NeckCD >NeckCD</option>
> 
> >  </select>
> 
> 
> 
> Why not go back to the bare code when asking a Q?
> 
> The extra code you showed only complicates the issue.
> 
> 
> 
> Try:
> 
> 
> 
> <select onclick='alert(this.value);'>
> 
>   <option value='1 selected' >One</option>
> 
>   <option value='2 selected' >Two</option>
> 
> </select>
> 
> 
> 
> 
> 
> 
> 
> -- 
> 
> Evertjan.
> 
> The Netherlands.
> 
> (Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#25685

PS <poonam.sachdeva5@gmail.com> wrote on 16 aug 2014 in 
comp.lang.javascript:

> Doesnt work in webkit.
> Works in FF.

Please do not toppost, 
as [that way?] you forget to answer my pertinent Q.

My code works fine in Chrome, which is Webkit.

My code also works fine in Chrome Mobile, which is Webkit.

So what browser do you mean that does not work?
What do you mean by "Doesnt work" exactly, btw?

> 
> On Friday, August 15, 2014 3:15:33 PM UTC-7, Evertjan. wrote:
>> PS <poonam.sachdeva5@gmail.com> wrote on 15 aug 2014 in
>> 
>> comp.lang.javascript: 
>> 
>> > I am trying to change my GUI on onclick. It works fine in google chrome
>> > and firefox but doesnt work in webkit browser. Tried to debug but it
>> > doesnt go into the function only.  
>> 
>> Is Chrome not a webkit browser?
>> 
>> > Have tried using addEventListeners but
>> > it doesnt work as well. it doesnt trigger the onclick.
>> 
>> Try:
>> 
>> object.onclick = function(){alert(this.value);};
>> 
>> > <select name="MetricType" id="MetricType"
>> > onclick="UpdateMetricFromGUI();"> 
>> >      <option value=CDatHT >CD</option>
>> >     <option value=HT >HT</option>
>> >    <option value=BowCD >BowCD</option>
>> >     <option value=NeckCD >NeckCD</option>
>> >  </select>
>> 
>> Why not go back to the bare code when asking a Q?
>> The extra code you showed only complicates the issue.
>> 
>> Try:
>> 
>> <select onclick='alert(this.value);'>
>>   <option value='1 selected' >One</option>
>>   <option value='2 selected' >Two</option>
>> </select>

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#25686

I have my own browser which is webkit as well. the code doesnt work in that one.

On Friday, August 15, 2014 3:40:30 PM UTC-7, Evertjan. wrote:
> PS <poonam.sachdeva5@gmail.com> wrote on 16 aug 2014 in 
> 
> comp.lang.javascript:
> 
> 
> 
> > Doesnt work in webkit.
> 
> > Works in FF.
> 
> 
> 
> Please do not toppost, 
> 
> as [that way?] you forget to answer my pertinent Q.
> 
> 
> 
> My code works fine in Chrome, which is Webkit.
> 
> 
> 
> My code also works fine in Chrome Mobile, which is Webkit.
> 
> 
> 
> So what browser do you mean that does not work?
> 
> What do you mean by "Doesnt work" exactly, btw?
> 
> 
> 
> > 
> 
> > On Friday, August 15, 2014 3:15:33 PM UTC-7, Evertjan. wrote:
> 
> >> PS <poonam.sachdeva5@gmail.com> wrote on 15 aug 2014 in
> 
> >> 
> 
> >> comp.lang.javascript: 
> 
> >> 
> 
> >> > I am trying to change my GUI on onclick. It works fine in google chrome
> 
> >> > and firefox but doesnt work in webkit browser. Tried to debug but it
> 
> >> > doesnt go into the function only.  
> 
> >> 
> 
> >> Is Chrome not a webkit browser?
> 
> >> 
> 
> >> > Have tried using addEventListeners but
> 
> >> > it doesnt work as well. it doesnt trigger the onclick.
> 
> >> 
> 
> >> Try:
> 
> >> 
> 
> >> object.onclick = function(){alert(this.value);};
> 
> >> 
> 
> >> > <select name="MetricType" id="MetricType"
> 
> >> > onclick="UpdateMetricFromGUI();"> 
> 
> >> >      <option value=CDatHT >CD</option>
> 
> >> >     <option value=HT >HT</option>
> 
> >> >    <option value=BowCD >BowCD</option>
> 
> >> >     <option value=NeckCD >NeckCD</option>
> 
> >> >  </select>
> 
> >> 
> 
> >> Why not go back to the bare code when asking a Q?
> 
> >> The extra code you showed only complicates the issue.
> 
> >> 
> 
> >> Try:
> 
> >> 
> 
> >> <select onclick='alert(this.value);'>
> 
> >>   <option value='1 selected' >One</option>
> 
> >>   <option value='2 selected' >Two</option>
> 
> >> </select>
> 
> 
> 
> -- 
> 
> Evertjan.
> 
> The Netherlands.
> 
> (Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#25687

On Friday, August 15, 2014 3:43:35 PM UTC-7, PS wrote:
> I have my own browser which is webkit as well. the code doesnt work in that one.
> 
> 
> 
> On Friday, August 15, 2014 3:40:30 PM UTC-7, Evertjan. wrote:
> 
> > PS <poonam.sachdeva5@gmail.com> wrote on 16 aug 2014 in 
> 
> > 
> 
> > comp.lang.javascript:
> 
> > 
> 
> > 
> 
> > 
> 
> > > Doesnt work in webkit.
> 
> > 
> 
> > > Works in FF.
> 
> > 
> 
> > 
> 
> > 
> 
> > Please do not toppost, 
> 
> > 
> 
> > as [that way?] you forget to answer my pertinent Q.
> 
> > 
> 
> > 
> 
> > 
> 
> > My code works fine in Chrome, which is Webkit.
> 
> > 
> 
> > 
> 
> > 
> 
> > My code also works fine in Chrome Mobile, which is Webkit.
> 
> > 
> 
> > 
> 
> > 
> 
> > So what browser do you mean that does not work?
> 
> > 
> 
> > What do you mean by "Doesnt work" exactly, btw?
> 
> > 
> 
> > 
> 
> > 
> 
> > > 
> 
> > 
> 
> > > On Friday, August 15, 2014 3:15:33 PM UTC-7, Evertjan. wrote:
> 
> > 
> 
> > >> PS <poonam.sachdeva5@gmail.com> wrote on 15 aug 2014 in
> 
> > 
> 
> > >> 
> 
> > 
> 
> > >> comp.lang.javascript: 
> 
> > 
> 
> > >> 
> 
> > 
> 
> > >> > I am trying to change my GUI on onclick. It works fine in google chrome
> 
> > 
> 
> > >> > and firefox but doesnt work in webkit browser. Tried to debug but it
> 
> > 
> 
> > >> > doesnt go into the function only.  
> 
> > 
> 
> > >> 
> 
> > 
> 
> > >> Is Chrome not a webkit browser?
> 
> > 
> 
> > >> 
> 
> > 
> 
> > >> > Have tried using addEventListeners but
> 
> > 
> 
> > >> > it doesnt work as well. it doesnt trigger the onclick.
> 
> > 
> 
> > >> 
> 
> > 
> 
> > >> Try:
> 
> > 
> 
> > >> 
> 
> > 
> 
> > >> object.onclick = function(){alert(this.value);};
> 
> > 
> 
> > >> 
> 
> > 
> 
> > >> > <select name="MetricType" id="MetricType"
> 
> > 
> 
> > >> > onclick="UpdateMetricFromGUI();"> 
> 
> > 
> 
> > >> >      <option value=CDatHT >CD</option>
> 
> > 
> 
> > >> >     <option value=HT >HT</option>
> 
> > 
> 
> > >> >    <option value=BowCD >BowCD</option>
> 
> > 
> 
> > >> >     <option value=NeckCD >NeckCD</option>
> 
> > 
> 
> > >> >  </select>
> 
> > 
> 
> > >> 
> 
> > 
> 
> > >> Why not go back to the bare code when asking a Q?
> 
> > 
> 
> > >> The extra code you showed only complicates the issue.
> 
> > 
> 
> > >> 
> 
> > 
> 
> > >> Try:
> 
> > 
> 
> > >> 
> 
> > 
> 
> > >> <select onclick='alert(this.value);'>
> 
> > 
> 
> > >>   <option value='1 selected' >One</option>
> 
> > 
> 
> > >>   <option value='2 selected' >Two</option>
> 
> > 
> 
> > >> </select>
> 
> > 
> 
> > 
> 
> > 
> 
> > -- 
> 

Evertjan,

Is there any different way of executing a function when I change the items in dropdown instead of Onclick, onchange or AddEventListener
 

> > 
> 
> > Evertjan.
> 
> > 
> 
> > The Netherlands.
> 
> > 
> 
> > (Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#25693

PS <poonam.sachdeva5@gmail.com> wrote on 16 aug 2014 in
comp.lang.javascript: 

> Is there any different way of executing a function when I change the
> items in dropdown instead of Onclick, onchange or AddEventListener 

Please explain yourself, what do you mean by "change", while programming?

What is wrong with onclick for starters?

If onclick does not work, your code is the first suspect,
why would your code work better using other listeners?

I would like to help you, so please answer my questions.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#25692

PS <poonam.sachdeva5@gmail.com> wrote on 16 aug 2014 in
comp.lang.javascript: 

> I have my own browser which is webkit as well. the code doesnt work in
> that one. 

So what browser and o.s. is that?

What do you mean by "the code", your elaborate code, or my simple one?

Please do not toppost on usenet.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#25694

In article <ca8ad936-c1db-4a45-a9e5-ba4ec78a00b0@googlegroups.com>, PS
<poonam.sachdeva5@gmail.com> wrote:

> I have my own browser which is webkit as well. the code doesnt work in that
> one.

Do you mean you have written your own browser? If so then say so.

Onclick works fine here in Safari (a webkit browser).

-- 
"People don't buy Microsoft for quality, they buy it for compatibility
with what Bob in accounting bought last year. Trace it back - they buy
Microsoft because the IBM Selectric didn't suck much" - P Seebach, afc

[toc] | [prev] | [next] | [standalone]

#25689

Evertjan. wrote:

> Is Chrome not a webkit browser?

Since version 28 (more than a year ago) Chrome uses the Blink engine,
which is a fork of Webkit[1].

[1] <http://en.wikipedia.org/wiki/Google_Chrome>

-- 
Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

#25690

I tried with onchange it doesnt work as well,
Its strange as usually browser behaves the same as google chrome(both are webkit) but this time the code is working on chrome but not on my browser.


On Friday, August 15, 2014 4:21:01 PM UTC-7, Christoph M. Becker wrote:
> Evertjan. wrote:
> 
> 
> 
> > Is Chrome not a webkit browser?
> 
> 
> 
> Since version 28 (more than a year ago) Chrome uses the Blink engine,
> 
> which is a fork of Webkit[1].
> 
> 
> 
> [1] <http://en.wikipedia.org/wiki/Google_Chrome>
> 
> 
> 
> -- 
> 
> Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

#25691

PS wrote:

> I tried with onchange it doesnt work as well,
> Its strange as usually browser behaves the same as google chrome(both
> are webkit)

Google Chrome uses Blink, which is a fork of Webkit, as I already noted.
 I don't know which layout engine is used by "your own browser".

> but this time the code is working on chrome but not on my
> browser.

Maybe your browser is broken or you have to enable JavaScript.  It might
be useful to tell which browser you are using.

And because you might have missed it, because you are using the worst
interface to Usenet, namely Google Groups: please read and heed the
newsgroup's rules regarding posting:
<http://pointedears.de/scripts/faq/cljs/notes/posting/>.

-- 
Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

#25696

On Sat, 16 Aug 2014 02:09:55 +0200, "Christoph M. Becker"
<cmbecker69@arcor.de> wrote:

  <snip>
> And because you might have missed it, because you are using the worst
> interface to Usenet, namely Google Groups: please read and heed the
> newsgroup's rules regarding posting:
> <http://pointedears.de/scripts/faq/cljs/notes/posting/>.

You really shouldn't point newcomers to documents that have not gone
through a peer review process nor gone through an approval process.

  John

[toc] | [prev] | [next] | [standalone]

#25697

John Harris wrote:

> On Sat, 16 Aug 2014 02:09:55 +0200, "Christoph M. Becker"
> <cmbecker69@arcor.de> wrote:
> 
>   <snip>
>> And because you might have missed it, because you are using the worst
>> interface to Usenet, namely Google Groups: please read and heed the
>> newsgroup's rules regarding posting:
>> <http://pointedears.de/scripts/faq/cljs/notes/posting/>.
> 
> You really shouldn't point newcomers to documents that have not gone
> through a peer review process nor gone through an approval process.

I am wondering whether and when
<http://www.jibbering.com/faq/notes/posting/> has gone through a peer
review or an approval process.

But as you prefer I will point newcommers to this document and other
information on <http://www.jibbering.com/faq/>, which is unmaintained
since several years--a fact that is not likely going to change.  Suum
cuique.

-- 
Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

#25698 — FAQ (was: Onclick event doesnt work in webkit browser)

Christoph M. Becker wrote:

> John Harris wrote: 
>> On Sat, 16 Aug 2014 02:09:55 +0200, "Christoph M. Becker"
>> <cmbecker69@arcor.de> wrote:
>>> And because you might have missed it, because you are using the worst
>>> interface to Usenet, namely Google Groups: please read and heed the
>>> newsgroup's rules regarding posting:
>>> <http://pointedears.de/scripts/faq/cljs/notes/posting/>.
>> You really shouldn't point newcomers to documents that have not gone
>> through a peer review process nor gone through an approval process.
> 
> I am wondering whether and when
> <http://www.jibbering.com/faq/notes/posting/> has gone through a peer
> review or an approval process.

The „comp.lang.javascript FAQ“ [1] was based on discussions in the 
newsgroup, but I do not know to what extent this section is based on them.  
IIRC the previous maintainer, Garrett Smith, was criticized for not having 
run several changes through a peer review.  AIUI he abandoned maintainance 
in part for not having to face the mostly destructive criticism anymore.  To 
my knowledge there was no approval process – which to me is the whole point 
of having a maintainer: to have a person to whom you delegate the 
responsibility of making an informed decision based on what people think 
because it is too difficult, maybe even impossible, for all of them agree on 
a point.  That said, it is better to present a FAQ’s content as 
recommendations than as rules.

The „FAQ for comp.lang.javascript“ (see signature) is supposed to be based 
on discussions in the newsgroup as well, as I said when I announced it in 
December 2012 [2] following a discussion in the newsgroup and on 
Twitter [3].  Since then, I have received a little feedback from few people 
(including you, thank you again).  I am thinking of a slightly different 
approach to editing now that might improve the situation.

> But as you prefer I will point newcommers to this document and other
> information on <http://www.jibbering.com/faq/>, which is unmaintained
> since several years--a fact that is not likely going to change.  Suum
> cuique.

It is probably not a good idea to change one’s approach solely based on the 
opinion of a person who has hardly, if ever, contributed anything to this 
newsgroup in the sense that their contribution was on-topic.

So far, with changes that are merely editorial in nature, the “FAQ for 
comp.lang.javascript” is identical to the “comp.lang.javascript FAQ” (which 
is unfortunate as that means that for the most part it contains the same 
errors and outdated information; the changelog can confirm this).

___________
[1] <http://www.jibbering.com/faq/>
[2] <news:2715826.m0UDekTA75@PointedEars.de>
    <https://groups.google.com/forum/#!original/comp.lang.javascript/yvxh6sd5deU/OVlYGsRKIIYJ>  
[3] <https://twitter.com/PointedEars2/status/276293702794768384>
-- 
PointedEars, editor
FAQ: <http://PointedEars.de/faq> | SVN: <http://PointedEars.de/wsvn/>
Twitter: @PointedEars2 | ES Matrix: <http://PointedEars.de/es-matrix>
Please do not Cc: me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#25699 — Re: FAQ (was: Onclick event doesnt work in webkit browser)

On Sat, 16 Aug 2014 20:19:58 +0200, Thomas 'PointedEars' Lahn
<PointedEars@web.de> wrote:

  <snip>
> It is probably not a good idea to change one’s approach solely based on the 
> opinion of a person who has hardly, if ever, contributed anything to this 
> newsgroup in the sense that their contribution was on-topic.
  <snip>

It's a fact that in the last year or so there have been hardly any
questions about the ECMAScript language itself.

On the other hand, it is also a fact that too often it has been
necessary to explain to newcomers that what Thomas has written is
either wrong or misguided or far too dogmatic.

  John

[toc] | [prev] | [next] | [standalone]

#25700 — Re: FAQ (was: Onclick event doesnt work in webkit browser)

John Harris <niam@jghnorth.org.uk.invalid> wrote on 17 aug 2014 in 
comp.lang.javascript:

> On the other hand, it is also a fact that too often it has been
> necessary to explain to newcomers that what Thomas has written is
> either wrong or misguided or far too dogmatic.

'Dogma', methinks, is always wrong, 
in a discussion group argument should reign, 
not dogma or authority.

'Wrong' is all right, 
one should not stop posting in fear of being wrong.

'Misguided' is just being wrong 
induced by supposed dogma or authority.

By whom would you stipulate Thomas was misguided?

'Necessary to explain' is rather subjective,
please keep to the argumented way of stating that.

And:

'Too often' ??? How often would be acceptable?
Please, again, keep to the argumented way of stating that.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#25709 — Re: FAQ (was: Onclick event doesnt work in webkit browser)

On Sun, 17 Aug 2014 19:28:30 +0200, "Evertjan."
<exxjxw.hannivoort@inter.nl.net> wrote:

> John Harris <niam@jghnorth.org.uk.invalid> wrote on 17 aug 2014 in 
> comp.lang.javascript:
> 
> > On the other hand, it is also a fact that too often it has been
> > necessary to explain to newcomers that what Thomas has written is
> > either wrong or misguided or far too dogmatic.
> 
> 'Dogma', methinks, is always wrong, 
> in a discussion group argument should reign, 
> not dogma or authority.

I agree, though perhaps "argument" is a bit strong.
 
> 'Wrong' is all right, 
> one should not stop posting in fear of being wrong.

I agree, but only if others are permitted to notice and point out that
it's wrong,

> 'Misguided' is just being wrong 
> induced by supposed dogma or authority.
> 
> By whom would you stipulate Thomas was misguided?

By people who write *.de Usenet diktats, and by himself.
 
> 'Necessary to explain' is rather subjective,
> please keep to the argumented way of stating that.

Giving misleading information to students and beginners is a sin. I'm
agin' it.

> And:
> 
> 'Too often' ??? How often would be acceptable?
> Please, again, keep to the argumented way of stating that.

Stamping on someone for using a pen name : more than twice a year is
too often.

Stamping on someone for not giving a usable e-mail address : more than
twice a year is too often.

Stamping on someone for giving more than the name in an attribution :
more than twice a year is too often.

etc.

  John

[toc] | [prev] | [next] | [standalone]

#25712 — Re: FAQ (was: Onclick event doesnt work in webkit browser)

John Harris <niam@jghnorth.org.uk.invalid> wrote on 18 aug 2014 in 
comp.lang.javascript:

> Giving misleading information to students and beginners is a sin. I'm
> agin' it.

That would backfire, as you would need dogma, authority, or even your own 
authority, to define the specific instance of such primordal sin. 

Let us stay with discussing by logical argument only,
this being a discussion group, not a school nor a helpdesk.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#25701 — Re: FAQ

John Harris wrote:

> On Sat, 16 Aug 2014 20:19:58 +0200, Thomas 'PointedEars' Lahn
> <PointedEars@web.de> wrote:
> 
>> It is probably not a good idea to change one’s approach solely based on the 
>> opinion of a person who has hardly, if ever, contributed anything to this 
>> newsgroup in the sense that their contribution was on-topic.

I really appreciate your ongoing efforts to maintain the newsgroup's
FAQ. :)  Unfortunately, despite multiple rather lengthy discussions
during the last years, there has not been an agreement about the
maintainer of the official FAQ--so, if anybody complains that
<http://pointedears.de/scripts/faq/cljs/> is not the official FAQ, they
are right.

And I am finally sick of discussing this issue with pigheads, who prefer
an unmaintained FAQ with out-dated information over a FAQ that is
maintained by somebody they don't like, even when there are no
alternative volunteers.

> It's a fact that in the last year or so there have been hardly any
> questions about the ECMAScript language itself.

Well, for instance, you could have posted thoughts about ECMAScript.next
(which might start interesting and fruitful discussions), if the
official newsgroup FAQ didn't imply that only questions are welcome (and
this can't be changed, unfortunately).  Of course, the newsgroup charter
talks of discussions, but its newsgroup line is

| comp.lang.javascript Netscape Communications Corp.'s JavaScript
| language.

It is probably a good idea to stick with this charter as well as with
the out-dated FAQ, and merrily going on posting OT. ;)

-- 
Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.lang.javascript

csiph-web