InformAction Forums

I doubt the plugins work anymore except in 52, though last time used Adobe plugin was something like 15 years ago. And even if the plugins did work, NS could block them with the "object" option.

However, FF does offer option to open the PDF in external program.

In that case I think it might be best to allow resource (and chrome|moz-extension|about) URIs regardless of the policy, maybe, or am I missing some important case? Not sure if NS should interfere with PDF handling as FF itself offers plethora of user configurable ways to do it (pdf.js, external view...

Well, looks like FF 60 blocks content scripts from running in the PDF-viewer. This is what breaks NS. Not sure if intended, but it might be due to a fix for security vulnerability that allowed PDF-files to run scripts in the viewers context. (The very unhelpful and wrong popup message is NS bug thou...

@David_L: Unfortunately it's a internal webextension thing - nothing that end user can do about. Giorgio could make a workaround, but the problem is quite benign and simply refreshing clears it, so it likely doesn't warrant one. Better just wait for a FF fix. Can't find related report on Bugzilla th...

Sigh, why is FF 60 breakin so many things with NS...

Anyhow, not a NS bug. Apparently having content CSS matching about:blank and running at document_start is what breaks the page refreshing when navigating to about:blank. The CSS file doesn't even need to have anything in it!

Very nice!

And before anyone asks - you can initiate the editing with a drag and drop motion on the empty space, in case you manage to hide all your icons.

Well, like I said, can't reproduce the problem here. Only difference being that I'm on linux, but I doubt that has anything to do with it.

Got any other extensions or custom settings that might interfere with NoScript? Could you check if the problem persists on clean profile with only NoScript added?

I'm able to get the frames shown simply by having "frame" privilege set for komoot.de. You sure you have frames allowed for trusted sites?

NS: 10.1.8.1

As title states, inline scripts do not get the red marker for blocked script in the CUSTOM tab (or get counted in the badge).

Problem seems to be in RequestGuard.js:onViolationReport, which appears not to detect and handle properly the CSP violation inline scripts throw.

The problem does seem to relate to the cookies as you suspected in your first post. The page sets a set of cookies at first visit, but for some reason any subsequent page load with these cookies fails (connection time out). However, having javascript enabled loads a slightly different set of cookies...

This sites spam filter does get triggered bit too easy. Try putting whatever text causes the trigger in code tags.

Hard to say. Have not had such problems. You might want to simply just reset all related page settings to default and redo them before trying to delete any files.

The minimum privileges I need to get the twimg.com shown are:

...webfail.com - script
...twitter.com - script and frame

If that doesn't work, you could try disabling uBO and see if that helps.

You need to first enable webfail.com and twitter.com, and then reload the page. After that the twimg.com will appear in the list. This is because twimg assests are loaded by the aforementioned scripts and cannot be seen by NS before they have run.

It is possible. I can replicate the count badge loop on latest uBO with the steps above. However I cannot replicate the issue on yahoo.com with either uBO or NS alone.