NoScript and Priv8

[Cloude]

Hallo,

I really love the NoScript Addon for Firefox. Thank you for the great work. But since a few weeks I have some troubles with it. I’m using the Priv8 Addon too and some pages, like Youtube, do not working right when I opened them in a Priv8 window (it is a sondboxed tab). I cannot play the videos or using other scripted elements on the web pages. Of course I allowed the scripts in the settings of NoScript, but it do not help. Only when I allow all scripts globally (or disable NoScript), it works. In the past, I don’t have this problem and this problem only appears when I using Priv8 to open the webpages and only in the sandboxed webpages.
So maybe you can help me to solve the problem.
Maybe I have to change in the deeper settings of NoScript something, but I do not know what NoScript is blocking in the sandboxed tabs of Firefox. I allowed for the webpages every script that is needed to use the functionalities that I missing now.

Sincerely

Cloude

[therube]

> Priv8 Addon

URL?

[barbaz]

it's on AMO https://addons.mozilla.org/addon/priv8/

[Thrawn]

What appears on the NoScript menu when the sites don't work?

Anything in the Browser Console (Ctrl+Shift+J)?

It's possible that the Priv8 addon simply isn't playing nicely with other addons, in which case there probably wouldn't be any log or any easy workaround.

[Cloude]

What appears on the NoScript menu when the sites don't work?

Anything in the Browser Console (Ctrl+Shift+J)?

It's possible that the Priv8 addon simply isn't playing nicely with other addons, in which case there probably wouldn't be any log or any easy workaround.

Hi,

thats what I found inside the Brwoser Console:

NetworkError: A network error occurred. <unbekannt>
TypeError: extension.onTabClosed is not a function overlay.js:398:67
TypeError: target.tagName is undefined overlay.jsm:266:1
Sicherheitsfehler: Inhalt auf resource://id-at-baku-dot-priv8/priv8/data/wait.html darf chrome://priv8/skin/fonts/pt_sans-captionbold-webfont.woff nicht laden oder verlinken.
Sicherheitsfehler: Inhalt auf resource://id-at-baku-dot-priv8/priv8/data/wait.html darf chrome://priv8/skin/fonts/pt_sans-captionbold-webfont.ttf nicht laden oder verlinken.
TypeError: target.tagName is undefined overlay.jsm:266:1
NetworkError: A network error occurred. <unbekannt>
TypeError: target.tagName is undefined overlay.jsm:266:1

I don’t how to understand the errors and don’t know how to fix them. Can you help me?
Actually I do believe that the Priv8 and NoScript Addon do not work together since one of them get an update that occur the described issues. Deactivating the NoScript Addon makes the Priv8 Addon work nicely.

[barbaz]

It looks like extension conflict.

Actually I do believe that the Priv8 and NoScript Addon do not work together since one of them get an update that occur the described issues.

Does downgrading NoScript get it working with latest Priv8?
Does downgrading Priv8 get it working with NoScript latest development build?

In either case what's the last version that works?

[Lafuet]

Does downgrading NoScript get it working with latest Priv8?
Does downgrading Priv8 get it working with NoScript latest development build?

Thank you for your answer. Can you help me to find previous versions of NoScript. I don’t know where to look for.
Thank you in advance.

[barbaz]

Oh sorry.
Old NoScript @
https://addons.mozilla.org/addon/noscript/versions
*or*
https://noscript.net/feed?c=100&t=a

[Cloude]

Hello,
I downgraded NoScript to version 2.6.9.28 but the latest version of Priv8 still didn’t work right.
So I downgraded Priv8 to version 0.0.3.1 and installed the latest version of NoScript, but it do not solve the problem.
I tried to downgrade them both, NoScript to 2.6.9.28 and Priv8 to 0.0.3.1 but for my surprise they were still not working right together.
I didn’t aspect that. Because in the past they were working together.
Currently Im using FF 42.0.

[barbaz]

Has this been reported to the Priv8 dev(s)? If so, is there a link where we can read that discussion?

[Cloude]

Has this been reported to the Priv8 dev(s)? If so, is there a link where we can read that discussion?

Yes, I reported it to Priv8 devs about one month ago. There was only the possibility to do it via E-Mail, so the discussion is not public and I’m still waiting for the answer. I will let you know in this forum if I will get a solution or any feedback.

[barbaz]

Yes, I reported it to Priv8 devs about one month ago. [...] I’m still waiting for the answer.

That's a long wait. Let's see if Priv8 might be dead...

AMO all versions page:

Version 0.0.8.1-signed
Released March 30, 2015
Works with Firefox 26.0 and later

Dev site, last commit

Commits on Mar 30, 2015

@bakulf

0.0.8

Doesn't look good for it.

I will let you know in this forum if I will get a solution or any feedback.

Thanks.