by Tree » Sun Jan 07, 2018 12:23 am
f_seán wrote:Regarding the original issue, i had been going nuts trying to figure out what broke and discovered the exact same problem. If you prefer webextensions.storage.sync.enabled;false, i found that setting webextensions.storage.sync.serverURL to
https://0.0.0.0 doesn't break anything. (Originally i thought it might be the culprit, after checking through all the changes i had made. FF has a lot of annoying stuff in it. )
Applies to 10.1.6.2 & 10.1.6.3rc2 at least. Using FF 58.0b4 or 58.0b6. I am not sure if it is related to this (would it be?):
Code: Select all
v 10.1.3rc1
x Fixed NoScript back-end to work also if sync storage is disabled (thanks Rob Wu for reporting)
I still could not honestly say if it was working while appearing dead. This was a completely new install of FF Dev ed and NS 10.x and i didn't visit any visually busy sites that would make it obvious NS was working or not.
Are these two issues related? You found where version 10.1.3rc1 lists "Fixed NoScript back-end to work also if sync storage is disabled" but it still appears to require either webextensions.storage.sync.enabled set to True or atleast some URL listed for webextensions.storage.sync.serverURL rather than empty just to function at all. The browser console lists [NoScript] Cannot collect noscript activity data <unavailable> Could not establish connection. Receiving end does not exist even when webextensions.storage.sync.enabled is set to True if webextensions.storage.sync.serverURL is changed.
The mentioned
https://hackademix.net/2017/11/28/growi ... -1013-rcs/ post says that the Trusted not being able to save settings properly started with 10.1.3rc2 unless atleast one thing in addition to script is selected starting with 10.1.3rc3. Could it be that the "Fixed NoScript back-end to work also if sync storage is disabled" in 10.1.3rc1 not only didn't fix that as intended, since it still needs webextensions.storage.sync.enabled set to True or atleast some URL listed for webextensions.storage.sync.serverURL rather than empty, but introduced the bug not allowing Trusted settings to be saved with just script selected?
Might it be possible for NoScript to use the storage-sync.sqlite file to save settings for those using a Sync account but use the browser-extension-data storage file for those wanting webextensions.storage.sync.enabled off? Other web extensions do not require webextensions.storage.sync.enabled to be on and save their settings in their browser-extension-data folder storage file.
barbaz wrote:Tree wrote:I can not get it to do it for Trusted though as it has everything checked and I only want script. It loads Trusted with everything checked each time on browser open even though I set Trusted to be just script each time. The guides say to click the clock to make the settings permanent for Trusted but there is no clock on any scope other than Custom.
How do I set Trusted to be just script and have that selection saved permanently?
Apparently you can't. It's fallout from this -
https://hackademix.net/2017/11/28/growi ... -1013-rcs/
As workaround, you'll have to enable at least one other item. In case it helps you decide which to enable, here are descriptions of what the items are -
https://forums.informaction.com/viewtop ... 552#p93552
Thank you barbaz. That was taking me a lot of time to figure out as I thought it was something on my end. Given that Trusted settings are saved properly for any combo other than just script and five weeks have passed since that posted issue, is that as intended or a bug hoped to be fixed?
Re:
https://forums.informaction.com/viewtop ... 552#p93552 and having to enable at least one other item, which do you recommend? The least undesirable to me seems to be fetch, other or WebGL as long as WebGL is set to disable in abbout:config. Would checking WebGL in NoScript but setting it off in about:config be effective blocking it or does checking it in NoScript cause potential issues even if off in about:config?
[quote="f_seán"]Regarding the original issue, i had been going nuts trying to figure out what broke and discovered the exact same problem. If you prefer webextensions.storage.sync.enabled;false, i found that setting webextensions.storage.sync.serverURL to https://0.0.0.0 doesn't break anything. (Originally i thought it might be the culprit, after checking through all the changes i had made. FF has a lot of annoying stuff in it. )
Applies to 10.1.6.2 & 10.1.6.3rc2 at least. Using FF 58.0b4 or 58.0b6. I am not sure if it is related to this (would it be?):
[code]v 10.1.3rc1
x Fixed NoScript back-end to work also if sync storage is disabled (thanks Rob Wu for reporting)[/code]
I still could not honestly say if it was working while appearing dead. This was a completely new install of FF Dev ed and NS 10.x and i didn't visit any visually busy sites that would make it obvious NS was working or not.[/quote]
Are these two issues related? You found where version 10.1.3rc1 lists "Fixed NoScript back-end to work also if sync storage is disabled" but it still appears to require either webextensions.storage.sync.enabled set to True or atleast some URL listed for webextensions.storage.sync.serverURL rather than empty just to function at all. The browser console lists [NoScript] Cannot collect noscript activity data <unavailable> Could not establish connection. Receiving end does not exist even when webextensions.storage.sync.enabled is set to True if webextensions.storage.sync.serverURL is changed.
The mentioned https://hackademix.net/2017/11/28/growing-pains-1013-rcs/ post says that the Trusted not being able to save settings properly started with 10.1.3rc2 unless atleast one thing in addition to script is selected starting with 10.1.3rc3. Could it be that the "Fixed NoScript back-end to work also if sync storage is disabled" in 10.1.3rc1 not only didn't fix that as intended, since it still needs webextensions.storage.sync.enabled set to True or atleast some URL listed for webextensions.storage.sync.serverURL rather than empty, but introduced the bug not allowing Trusted settings to be saved with just script selected?
Might it be possible for NoScript to use the storage-sync.sqlite file to save settings for those using a Sync account but use the browser-extension-data storage file for those wanting webextensions.storage.sync.enabled off? Other web extensions do not require webextensions.storage.sync.enabled to be on and save their settings in their browser-extension-data folder storage file.
[quote="barbaz"][quote="Tree"]I can not get it to do it for Trusted though as it has everything checked and I only want script. It loads Trusted with everything checked each time on browser open even though I set Trusted to be just script each time. The guides say to click the clock to make the settings permanent for Trusted but there is no clock on any scope other than Custom.
How do I set Trusted to be just script and have that selection saved permanently?[/quote]
Apparently you can't. It's fallout from this - [url]https://hackademix.net/2017/11/28/growing-pains-1013-rcs/[/url]
As workaround, you'll have to enable at least one other item. In case it helps you decide which to enable, here are descriptions of what the items are - https://forums.informaction.com/viewtopic.php?p=93552#p93552[/quote]
Thank you barbaz. That was taking me a lot of time to figure out as I thought it was something on my end. Given that Trusted settings are saved properly for any combo other than just script and five weeks have passed since that posted issue, is that as intended or a bug hoped to be fixed?
Re: https://forums.informaction.com/viewtopic.php?p=93552#p93552 and having to enable at least one other item, which do you recommend? The least undesirable to me seems to be fetch, other or WebGL as long as WebGL is set to disable in abbout:config. Would checking WebGL in NoScript but setting it off in about:config be effective blocking it or does checking it in NoScript cause potential issues even if off in about:config?