Firefox 30.0 blocks Preview of e.g. nytimes.com in Feedly. Disabling protection requires reloading Feedly. How to disallow protection for e.g. Feedly?
Firefox 30.0 blocks in-line Preview of e.g. nytimes.com in Feedly. Blocking a combination of https://feedly.com and http://nytimes.com seems overly protective. Disabling the protection is clumsy, requiring a reload of Feedly, and it must be repeated after every reload of Firefox. How to disallow the protection of Feedly.com more permanently?
P.S. I do use NoScript - it's set to not interfere in this matter . . .
Chosen solution
OOOOps? 10th July the FF blocking problem disappeared. The only changes to the system (Mac OS 10.9.4) or Firefox that I know of are a Flash update yesterday and a NoScript update today. Other changes could be automatic updates from Sophos and Google that shouldn't interfere with this matter. I suppose the matter was resolved (for the time being) by a small change somewhere in the web programming/scripting triangle of feedly.com, nytimes.com and NoScript, possibly with an assist from Adobe Flash.
Sorry to have bothered reader(s) of this support thread.
salbjerg
Read this answer in context 👍 0All Replies (6)
yup, got your point....
While opening such pages....not only those site...site which contains....malware...etc.... those are blocked by anti-virus in our machine.
1.so, if you opens, those kind of pages, a pop-up will come...at that you select, always allow option.
(or)
2.Ultimately you have to remove anti-virus from your machine, but its impossible to remove. Kindly go with option(1) mentioned above.
By that way, we can overcome your problem. Thats not an error generated by firefox.browser.
Moreover , firefox protect us from malware sites. still, your needed any assitance more means ping me back !
Thank you ! Hav a nice day !
regards,
Bala Subramaniyan
I see no pop-up. I have to click the "shield" (?) icon to the left of URL. That lets me disable protection, but only for the current session. --- My problems are: 1) the procedure is cumbersome, and 2) this specific Firefox protection is over-zealous, taking the user hostage instead of letting the user (ultimately) decide what to block and when. --- ad 2) I generally appreciate Firefox focusing on security, only this specific instance feels like big brother taking over "my" browser.
Thanks for supporting firefox !
In security, aspects Firefox stands +1 !
still, your problem not solved na, do one thing uninstall the browser & data of the browser completely....download a updated one & install it !
after that, you open that site....if any pop-up comes means,...do what i said before to you !
ping back, if not solved means.....Am here to help my sister !
thank you,
regards, Bala Subramaniyan
I’m seeing exactly the functionality described at
https://support.mozilla.org/en-US/kb/how-does-content-isnt-secure-affect-my-safety?
including screen-shots and the very short-lived “Disable Protection on This Page” preference alluded to in the statement “to ( . . . ) re-block mixed content, re-visit the page in a new tab”.
Therefore, I don’t think nuking my Firefox installation will do much good.
What I’m asking for, is a way to have “Disable Protection on This Page” work until further notice (across tabs/windows/sessions); if not as part of the GUI, then a pref in about:config.
BTW, the functionality of the “Keep Blocking - Not Now” preference is not clear.
Maybe the developer(s) of the blocking feature really meant to implement both a “Not Now” pref (valid only in the current tab) AND a general “Disable Protection on This Page” (valid accross sessions) — only it didn’t work?
If any emgerency work means....removing blocking....do your work....those malware wont effect much....Moreover, i will bring this issues to higher peoples of mozilla...Soon we will find the better solution !
thank you !
Regards, Bala Subramaniyan
Modified
Chosen Solution
OOOOps? 10th July the FF blocking problem disappeared. The only changes to the system (Mac OS 10.9.4) or Firefox that I know of are a Flash update yesterday and a NoScript update today. Other changes could be automatic updates from Sophos and Google that shouldn't interfere with this matter. I suppose the matter was resolved (for the time being) by a small change somewhere in the web programming/scripting triangle of feedly.com, nytimes.com and NoScript, possibly with an assist from Adobe Flash.
Sorry to have bothered reader(s) of this support thread.
salbjerg