InformAction Forums

It seems to me that firefox 28 has broken local linking? I have 6 computers in my domain that all used FF27 just fine yesterday. They updated today to FF28 and we also updated the NoScript at the same time to latest stable. Since then, I have not been able to successfully open a local link! I have tried devel build. I have created a new FF profile to test. I have run with only this 1 addon installed.

We use NoScript for our internal domain to make it possible to open links that resides on network drives. Normally, we are able to whitelist our domain, 'Allow Local Links' on the trusted advanced tab, and then click a link to open it.
Now: It silently fails. Gives no response at all. Any ideas on what broke?

If you revert to an earlier NoScript, http://noscript.net/feed, are you back working?

I didn't try that, however, I did roll back to FF27 without changing anything else and now it all works just great!

I'll put FF28 on a test machine and see if older version of NoScript works.

Using FF28 with noscript 2.6.8.18 did NOT work.
Using FF27 with noscript 2.6.8.18 does work.
Using FF27 with noscript 2.6.8.19 does work.

Anything else you want me to test?

In Fx28, when local links fail, anything related in the Browser Console? (Ctrl-Shift-J)
Also, are you able to test Gecko 29 (Fx29, SeaMonkey 2.26 Aurora), and if so, does it work there?

Security Error: Content at https://secure....ocessInvoice.aspx?id=2&status=8 may not load or link to file://///192.168.1...

Using Firefox 29 and noscript 2.6.8.18:
--
Security Error: Content at https://secure..../ProcessInvoice.aspx?id=2&status=8 may not load or link to file://///192.168.1...
A promise chain failed to handle a rejection.

Date: Thu Mar 27 2014 11:58:01 GMT-0600 (Mountain Standard Time)
Full Message:
Full Stack: JS frame :: resource://gre/components/nsLivemarkService.js :: LS_getLivemark/< :: line 405
JS frame :: resource://gre/components/nsLivemarkService.js :: ETAT_handleCompletion :: line 144
native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0 nsLivemarkService.js:405

devinname wrote:Using Firefox 29 and noscript 2.6.8.18:
--
Security Error: Content at https://secure..../ProcessInvoice.aspx?id=2&status=8 may not load or link to file://///192.168.1...

Just tested with FF 29 and NoScript 2.6.8.19 and I get the same error still.

This behavior change is expected, even though undesired, because NoScript doesn't rely on CAPS anymore in Firefox 28 and above.
I'm gonna try working around the surprise factor in next release, but in the meanwhile you can revert to the traditional means to enable local links, which used to interfere with CAPS-based NoScript and was therefore advised against.

Giorgio Maone wrote:you can revert to the traditional means to enable local links, which used to interfere with CAPS-based NoScript and was therefore advised against.

I found this page as I was looking for an alternative to NoScript. However, I must have been doing it wrong or something. I was under the impression that we should be making changes in 'about:config' as I found this warning in the prefs.js file:
* To make a manual change to preferences, you can visit the URL about:config

However, while I was in about:config, I was trying to add those strings, but Firefox wouldn't accept them. other string it was doing fine (stuff like text.string = TEXT), but adding 'capability.policy.policynames' wouldn't show up after I entered the string name and a value.

Editing the prefs.js file with Firefox 29 allowed me to get the changes into the system and recognized. Thus, my about:config looks like this: http://imgur/0Rpl2Qm. This should mean that when I am at a page like https://secure.rrrr rrr.com/ProcessInvoice.aspx?id=2&status=8, local links should work, right?

In the dev console, I still get the same security error that I have posted above. Am I using the prefs.js file wrong? Thanks so much for all y'alls help!

and I will note that I have also removed NoScript before trying this (I saw something about NoScript conflicting with edits to this stuff).

devinname wrote: about:config looks like this: http://imgur/0Rpl2Qm.

I relaized that this picture did not include the policynames user_pref. I have added that properly to theprefs.js file and still can't open local file links. In about config, it shows up as:

capability.policy.policynames;localfilelinks

So that should be working good and fine...

That approach won't work in Firefox >= 29 because Mozilla completely removed CAPS. And it's not that your creating the prefs in about:config wasn't working in Fx28, it's that about:config hides capability.* preferences by design.

devinname wrote:and I will note that I have also removed NoScript before trying this (I saw something about NoScript conflicting with edits to this stuff).

That no longer applies to Firefox 28+ as NoScript is not using CAPS in Gecko >= 28.

barbaz wrote:That approach won't work in Firefox >= 29 because Mozilla completely removed CAPS. And it's not that your creating the prefs in about:config wasn't working in Fx28, it's that about:config hides capability.* preferences by design.

devinname wrote:and I will note that I have also removed NoScript before trying this (I saw something about NoScript conflicting with edits to this stuff).

That no longer applies to Firefox 28+ as NoScript is not using CAPS in Gecko >= 28.

So there is nothing that can be done to enable local links in FF28+ due to removing CAPS?

CAPS is still in Firefox 28 but it's deprecated.
It's Firefox *29* that removes it.