The v14 branch has the same problems the v13 branch had originally with the Noscripts extension: Some 3rd party scripts cannot be white/black listed when using SSL because HTML5 storage cannot be read.
In order to be able to manage external scripts we have to enable 3rd party cookies, which is bad.
Can this be fixed or were security measures tightened?
Problem with HTML5 storage, cookies and extensions
Re: Problem with HTML5 storage, cookies and extensions
Hi,
Try ScriptNo extension.
Far better than NoScripts
And maybe solve your problem...
Try ScriptNo extension.
Far better than NoScripts
And maybe solve your problem...
Re: Problem with HTML5 storage, cookies and extensions
Thanks for the tip. I'll see if it works on the sites that had problems.
Re: Problem with HTML5 storage, cookies and extensions
So, I've tried and there are still problems
On piwik.org per example, the domain can't be whitelisted.
It usually happen when social network sharing is enabled on a site and 3rd party cookies need to be set.
This was fixed in a later version of v13, so there must be something that can be done on the iron side of things.
On piwik.org per example, the domain can't be whitelisted.
It usually happen when social network sharing is enabled on a site and 3rd party cookies need to be set.
This was fixed in a later version of v13, so there must be something that can be done on the iron side of things.