Temporarily disabling NoScript

[UnixRonin]

During the course of trying to troubleshoot a problem with Google Plus, I went through and progressively disabled all of my add-ons to determine whether any of them was causing the problem. This worked just fine up until the point at which I hit NoScript, which apparently hooks the disable action and asked me whether I wanted to disable everything or just script blocking. I selected script blocking only, but NoScript then showed as fully disabled in my add-ons list because there's no interface for marking an add-on as partially disabled.

This is a clever technical trick, but I'm not sure it's actually helpful. I ended up uncertain of whether I'd actually fully disabled NoScript or not, and whether I successfully fully re-enabled everything again afterwards.

(For the record, the Google Plus problem - a non-functional notification widget - did not appear, from my testing, to be the fault of NoScript, or any other of my add-ons for that matter. I suspect a compatibility problem between Google Plus and Firefox 22.0.)

[Giorgio Maone]

I selected script blocking only, but NoScript then showed as fully disabled in my add-ons list because there's no interface for marking an add-on as partially disabled.

If you selected "No, just stop blocking script" then NoScript should have been show as still enabled.
Not sure what happened in your case (either you hit the wrong button or a bug).