InformAction Forums

Earlier today I upgraded FF to v53.0 and now my local .htm file links will only open when NoScript 5.0.2 is disabled. There is no error message or other indication of failure. The .htm file simply fails to open. Pasting the file:\\\ link into the FF address bar then hitting enter results in the address bar being cleared. Is this problem unique to me or is it a confirmed issue.

The file links open fine in IE and in FF when NoScript is disabled.

Same Problem after update to FF 53.0
I hope it will be fixed in the next update of NoScript or some one can tell what to change in setting

Options > Advanced > Trusted > Allow local links

Disable this option, and file-URLs will be loaded again.

Possible reason: https://blog.mozilla.org/addons/2017/02 ... firefox-53

General, point 2: Use a separate content process for file:// URLs. This slightly changes the behavior of _openURIInNewTab.

Thanks for the workaround Stefan.

Disabling "Allow local links" is counter-intuitive to allowing local files so I hope this gets fixed soon.

Another thread suggests this problem with Allow local links may be extension conflict - viewtopic.php?f=10&t=22562

Does disabling all extensions other than NoScript get it working? (Tools > Add-ons Manager)

Same problem here. Deactivated all other addons will not help.

If I deactivate this will do the trick as a workaround.

Only difference with all deactivated other addons is that I can see a URL in the adressbar now (e.g. file:///C:/index.html) but with no effect. Bug stays the same.

it might be a red herring (and/or i total misunderstand the circumstances), but prompted by the reference to the "separate content process for file:// URLs" change in firefox 53...

the ubufox (ie "ubuntu modifications") add-on disables (either directly or incidentally) "multiprocess windows". about:support shows "Multiprocess Windows: 0/1 (Disabled by add-ons)" when ubufox is enabled and "1/1 (Enabled by default)" when disabled.

(i couldn't find a setting to enable/disable multiprocess windows in about:config to do it manually to test that it's specific to that and not to something else related to ubufox.)

now why ubufox works fine by itself and noscript works fine by itself, but if you have ubufox and noscript and "Allow local links", then it breaks file:// urls, that's left to be explained by someone more familiar with noscript's implementation.

undefined wrote:(i couldn't find a setting to enable/disable multiprocess windows in about:config to do it manually to test that it's specific to that and not to something else related to ubufox.)

Try doing the opposite of this - https://superuser.com/a/1108314

tl;dr browser.tabs.remote.autostart.2 = false

i'm able to recreate the problem apart from any extension (in my case ubufox) by setting browser.tabs.remote.autostart.2 to "false" (from the default of "true", though it says in about:config that it's technically "user set", but if i reset the value then it comes back up automatically as "true", so i don't know what definition of "user set", versus "default", firefox is using ).

so, if:

• browser.tabs.remote.autostart.2 = false
• "Allow local links" enabled

then:

• file:// urls don't work

i presume that the problem is noscript, specifically its "Allow local links" functionality, behaving badly (or triggering a firefox bug) when multi-process firefox is disabled (either implicitly, eg ubufox extension, or explicitly, ie browser.tabs.remote.autostart.2).

maybe i'll look in noscript and see where all that option is used (to see what code it enables).

Problem just started for me, with latest FF. Win-10. Tried suggestions above. Disableing NoScript fixes, but I cant live that way!

Partial Work around/perhaps a hint as to whats happening. I only need much access to one file, so as a trial, rather than a bookmark, I made a desktop shortcut to that file. It works. No idea what the difference between a bookmark to a file, and a file shortcut is, maybe someone smarter can use this hint to work on a real fix.

Suppose it would be helpful to know:

OS
32 or 64-bit FF
e10's enabled or not
& then testing in a new, clean Profile, with only NoScript installed - at its default settings

Seems to work if you create a new boolean param with about:config You can test if multiprocess is enabled in about:support - "Multiprocess Windows"
see here https://superuser.com/questions/1029400 ... refox-beta

Celebrated too soon. With NoScript did not work anymore. There is nothing in the dropdown you can click on.

I get the same problem with FF 53.0 and NoScript 5.0.3....

Disabled NoScript and file open works...