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


Groups > comp.lang.javascript > #26844

Re: FireFox onclick problem

Path csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!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" <syntel@cox.net>
Newsgroups comp.lang.javascript
Subject Re: FireFox onclick problem
Date Tue, 10 Feb 2015 16:21:07 -0700
Lines 52
Message-ID <cjvi3aFctdrU1@mid.individual.net> (permalink)
References <cjuvd1F7thrU1@mid.individual.net> <mbe16v$vj2$1@solani.org>
X-Trace individual.net SlKeMLPUeGjgBDbBriOkjA3fzY5X521goImoBtcL6h/W3fNKkZ
Cancel-Lock sha1:5pQlllaliTOI5aOLQUEArNNWv6Q=
X-Priority 3
X-MSMail-Priority Normal
X-Newsreader Microsoft Outlook Express 6.00.2900.5931
X-RFC2646 Format=Flowed; Original
X-MimeOLE Produced By Microsoft MimeOLE V6.00.2900.6157
Xref csiph.com comp.lang.javascript:26844

Show key headers only | View raw


Hi Christophe:

>
> Maybe JavaScript is disabled completely, or some installed plugin blocks
> the execution?  Maybe Content Security Policy[1] is enabled?

    Correct !

    A couple of weeks ago, I had complained about not being able to 'Disable 
Javascript' for testing.  I then reposted about finally finding the 
'about:config settings.

    I did my testing then I 'thought' that I had left Javascript enabled..

    So, I went back in with my 'new' firefox debug package, and tried to 
follow what was going on.  The FF debug package *said* that FF was disabled 
!

    This rang firebells in my head !

    So, I dived deep into about:config, and it said FF was *enabled*

    I toggled it a couple of times to ensure it really *was* enabled, then 
exited and tried my test again.

    It now works correctly -- but I can't understand the enabled / disabled 
settings and their transience ?? .

Anyway, thank you for confirming what I did !

    and thanks to EvetJan and Joao for their help.

-Mel

(so now I'm going to dig deeper into Firebug.)



>
> I suggest to place a quick debug statement at the beginning of
> hidenotice() to see whether the function is called at all, e.g.
>
>  alert('hidenotice');
>
> And, of course, have a look at the error console of Firefox.
>
> [1] <http://en.wikipedia.org/wiki/Content_Security_Policy>
>
> -- 
> Christoph M. Becker 

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


Thread

FireFox onclick problem "Mel Smith" <syntel@cox.net> - 2015-02-10 11:02 -0700
  Re: FireFox onclick problem "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2015-02-10 20:32 +0100
    Re: FireFox onclick problem "Mel Smith" <syntel@cox.net> - 2015-02-10 14:55 -0700
  Re: FireFox onclick problem Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2015-02-10 19:34 -0200
    Re: FireFox onclick problem "Mel Smith" <syntel@cox.net> - 2015-02-10 15:21 -0700
  Re: FireFox onclick problem "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-02-10 23:37 +0100
    Re: FireFox onclick problem "Mel Smith" <syntel@cox.net> - 2015-02-10 16:21 -0700

csiph-web