[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnuzilla] A need of a paradigm shift for solving the JavaScript

From: Jeffrey 'jf' Lim
Subject: Re: [Bug-gnuzilla] A need of a paradigm shift for solving the JavaScript Trap
Date: Tue, 18 Nov 2014 13:28:59 +0800

On Tue, Nov 18, 2014 at 12:54 PM, Nik Nyby <address@hidden> wrote:
>> would it simply be better to have a (better?) javascript
>> debugger/logger? I have personally wished for something like this. A
>> "supercharged" debugger with logger that truly helps u understand wth
>> is going on with a script/s.
> What do you need this debugger to do? The JavaScript debugger that comes
> with Firefox / IceCat works fine for everything I need it to do.

(Some background; but for the TL;DR, see the list below):
I am looking for a debugger *PLUS Logger*. I dont want to have to
trace through everything. But I would be *especially* interested to
know if the javascript makes some call somewhere (maybe set a
breakpoint too! with the option to modify or block the call before
continuing) to some server....

Here's a list of ideas:
- log calls, including arguments, sent data and results (the very act
of logging is important, because sometimes stuff will be broken / the
behaviour will change due to the loss of focus of mouse/keyboard due
to a debugger being activated). This log format should be open, and
- set breakpoint on network activity or other insidious activity (in
my mind, that would include code that runs "onmouseover", and

I hope this explains things better? And just to be clear, I understand
that there will be work involved; and whoever chooses to undertake
this, I will be most appreciative. Or if there's some way already to
do this right now, I would appreciate info. In the meantime... does
anybody see the need for this?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]