Tracking Protection conflicts with NoScript
Hi,
A particular site I visit employs Google Custom Search, for which I need to set googletagmanager.com as trusted in NoScript. The functionality of the Custom Search breaks if Tracking Protection is enabled but is not rectified by disabling just for the said site.
Should it be that case that I need to disable Tracking Protection globally, for the Google Custom Search to function correctly, if I have if I have NoScript enabled?
Thanks for any info.
Ausgewählte Lösung
Hey, just stumbled on an odd and not necessarily intuitive solution.
I changed Firefox's default search engine from Google to DuckDuckGo - problem solved, toggling point 6 now works!
The site in question is a UK online newspaper (term used loosely) mirror.co.uk with GCS being accessed via the 'magnifying glass' top right - I'd suggest using an ad blocker if you are tempted to visit o.O
Thanks again.
Diese Antwort im Kontext lesen 👍 0Alle Antworten (5)
see this page under Turn off Tracking Protection for individual sites:
I think Tracking Protection and NoScript will each independently block Google Analytics domains, and you need to make an exception with each of them individually.
If you are entering an exception manually, Firefox is a bit picky about the formatting. You might find it easier to use the site information panel that drops from the left end of the address bar (a shield icon will be displayed when Tracking Protection is blocking content).
Thanks for the replies,
To clarify the situation - using a clean profile:
- Firefox Tracking Protection - disabled by default
- Visit site in question - Google Custom Search works
- Install NoScript - GCS fails
- Set googletagmanager.com as an exception (trusted) in NS - GCS works
- Enable FF TP in the 'hamburger' menu - GCS fails
- Click the 'Disable For This Site' button, using the shield icon in the address field - GCS still fails
- Disable FF TP in the 'hamburger' menu - GCS works again
@FFus3r: "Turn off Tracking Protection for individual sites" - Does not help in this instance (point 6 above).
@jscher200: "you need to make an exception with each of them individually" - Like I did at points 4 & 6 - If I'm not understanding you correctly, could you enlighten me more - perhaps if I provide the site address?
I can't see anything relevant when using "the site information panel".
Thank you for any further help.
Hi fade2gray, I haven't heard of #6 failing before. Can you link to a site that has this problem?
Ausgewählte Lösung
Hey, just stumbled on an odd and not necessarily intuitive solution.
I changed Firefox's default search engine from Google to DuckDuckGo - problem solved, toggling point 6 now works!
The site in question is a UK online newspaper (term used loosely) mirror.co.uk with GCS being accessed via the 'magnifying glass' top right - I'd suggest using an ad blocker if you are tempted to visit o.O
Thanks again.
Geändert am