[UNRELATED] pentadactyl + noscript

[Tom T.]

Hi,

I use Pentadactyl, a firefox addon that makes firefox more vim-like. When I use its command :tabonly which means "close all other tabs", I get an InternalError from NoScript:

chrome://noscript/content/noscriptOverlay.js: 1572: InternalError: too much recursion

As it's a noscript related error I thought I'd post it here, am I right to do so and can it be fixed?

[Tom T.]

I'm not familiar with that add-on, and was going to suggest asking them whether they've had any others report such an issue, but a very quick search of their Help site turned up:
http://groups.google.com/group/pentadactyl/browse_thread/thread/561319694898f59/cece3ffc0654c6e9?lnk=gst&q=noscript#cece3ffc0654c6e9

On Mon, Feb 13, 2012 at 01:05, eqyiel <eqy...@gmail.com> wrote:
> Hi,
> This may be old news to you, but I haven't been able to find any
> discussions on the web about this. Since a while ago, NoScript doesn't
> work with Pentadactyl like it used to.

Perhaps you're not aware that Pentadactyl's NoScript functionality is
a plugin. You can get it from here
http://dactyl.sourceforge.net/pentadactyl/plugins#noscript-plugin.
Place it in ~/.pentadactyl/plugins.
--
Denis Kasak

Does this fix it for you?


ETA:

I should add that since they've created their own plug-in, which alters NoScript's behavior, any further support issues should go to them.
Also, we can't be responsible if any NoScript protection or functionality is lost, nor for the consequences thereof.

I was surprised to see this default:

'script'
boolean(default: noscript)

When on, all sites are allowed to execute scripts and load plugins. When off, only specifically allowed sites may do so.

That seems backwards. With NS, when on, only specifically allowed sites may load executable content. When disabled, all can.
Perhaps I'm misunderstanding them, but I just wanted to give a heads-up.

[tango]

Hi Tom,

Well, the NoScript plugin they provide gives me mixed results. But ok I'll talk over at their side, see what they say.

By the way... as with vim, pentadactyl's settings are toggable with either "foo" (turn foo on) and "nofoo" (turn foo off). E.g. "set online" versus "set noonline." The default setting for here seems to be "noscript" which means 'noscript is on.' it might seem backwards but for people like me who are so used to vim it's no problem.

I'll keep you posted, thanks for the reply.
-T

[Tom T.]

Well, the NoScript plugin they provide gives me mixed results. But ok I'll talk over at their side, see what they say.

It really does seem like the ball is in their court now, since their add-on takes over control of NS. But by all means, do let us know what they tell you.

By the way... as with vim, pentadactyl's settings are toggable with either "foo" (turn foo on) and "nofoo" (turn foo off). E.g. "set online" versus "set noonline." The default setting for here seems to be "noscript" which means 'noscript is on.' it might seem backwards but for people like me who are so used to vim it's no problem.

I sort of guessed that, but not being a Vim user, wasn't familiar with the syntax. Thanks for confirming.
It still dosn't explain this:

When on, all sites are allowed to execute scripts and load plugins. When off, only specifically allowed sites may do so.

If :noscript = ON, then only allowed sites should run script.
:nonoscript = OFF = all are allowed. Still backwards IMHO, but since I don't use the add-on...

[tango]

It still dosn't explain this:

When on, all sites are allowed to execute scripts and load plugins. When off, only specifically allowed sites may do so.

If :noscript = ON, then only allowed sites should run script.
:nonoscript = OFF = all are allowed. Still backwards IMHO, but since I don't use the add-on...

Yes, I suppose it can be confusing.

So let me explain better -- a user does not set "nonoscript", a user sets either "script" or "noscript." Just like "hlsearch" versus "nohlsearch", "ignorecase" versus "noignorecase". Hey, I didn't invent it!

So: "script" deactivates the plugin. "noscript" activates it.

[Tom T.]

So: "script" deactivates the plugin. "noscript" activates it.

Ahhhhh!

"script" lets script run.
"noscript" activates NoScript.

Finally!

... although, TBPH, we see various ways to "disable NoScript" or "allow script globally", but I personally have never seen "script" as the opposite of "NoScript".

Hey, I didn't invent it!

I hear you!