InformAction Forums

Interestingly, seems fixed in rc4.

We're talking FF nightly? And just what FF version is that at this point? Ah,　Yes, I test with FF nightly(0908). I'm not sure it happens on release version or old nightly. Do other extensions' popups work? As far as I see, ublock origin shows its popup correctly and NoScript's popup works normally ...

At least on 10.1.9.2rc3 with latest nightly, NoScript's popup doesn't show any contents. When I try to show Noscript popup, Browser Console said, this.viewNode is null, can't access property "removeEventListener" of it 2 ExtensionPopups.jsm:486 attach resource:///modules/ExtensionPopups.jsm:486:5 In...

With 10.1.8.3rc10, on NoScript popup, First row doesn't show a current setting when the setting is default.

Image is https://i.gyazo.com/ddcc46d16c446af6a80 ... cccb2e.png

Simply, due to a miss in code...

In storage.js

async set(type, obj) {
return await this.safeOp("set", type, keys);
}

variable name mismatch between obj and keys...
Probably, fixed in future release.

With 1108 nightly, NoScript can't work correctly. Prefs aren't displayed, some sites returns error. NoScript uses nsIPrefBranch.setComplexValue which behavior was changed by a patch in Bug 1414096 . So that, NoScript no longer works with 1108 nightly. ADDITION: Once, Bug 1414096 is reopened by backo...

Giorgio Maone wrote:Please check latest development build 5.1.0rc2, thanks.

Confirmed fixed. Very thanks!

On 2017-09-23 nightly with NoScript, contents in iframe aren't loaded at all. STR: Open http://masaboo.cside.com/new_html1/ht_44.htm. Expected Results: HTML in iframe is displayed. Actual Results: Completely blank in iframe. Is Bug 1402102 related? It removes nsIDOMHTMLObjectElement which is used in...

On 0808 nightly, NoScript shows exception "this.mappings is undefined" and doesn't work at all.

Root cause is that Bug 1374847 was fixed.
nsIPrefBranch2 no longer exists, so Qi of nsIPrefBranch2 at ScriptSurrogate.js(line 22) fails.

This isn't urgent problem because dom.ipc.process pref is set to 1 currently. But when dom.ipc.process is set to enough large for each tab to have their own process(This is future work for firefox), NoScript behaves unexpectedly. STR: 0. Set dom.ipc.process enough large value. 1. Open New tab and op...

STR: 1. Open http://www.yahoo.co.jp/ and allow yahoo.co.jp in NoScript popup. 2. Close Firefox and Open. Expected Result: Javascript works on http://www.yahoo.co.jp/ Actual Result: http://www.yahoo.co.jp/ says "Javascript isn't enabled". To work normally, we need to disallow yahoo.co.jp on...

Reference: https://bugzilla.mozilla.org/show_bug.cgi?id=1220564

I have seen same problem in https://p.eagate.573.jp/gate/p/login.html?___REDIRECT=1. And in my build, get these error message. Error: Error: Failed to load script (nsresult = 0x805e0006) Source File: https://www.google.com/recaptcha/api2/w ... 1112120204 Line: 1 Error: : NS_ERROR_FAILURE: Source Fil...

This is e10s related warning because NoScript isn't ready for e10s now.
If you get worried about them, you should disable e10s by uncheck "Enable multi-process...".

In Bug 1134196, a patch to fix the cause of crash is landed.