Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Norton 360 does not pick up tracking cookies after updating to firefox 17.0

  • 1 (رد واحد)
  • 1 has this problem
  • 5 views
  • آخر ردّ كتبه the-edmeister

more options

With firefox 17.0 Norton 360 does not pick up tracking cookies that were picked up with firefox 16.0.2. Uninstalled 17.0 and and reinstalled 16.0.2 - tracking cookies are picked up - updated to 17.0 and again no tracking cookies. I did not see anything in release note that would seem to reflect this situation. asked this question at 08:57 PST 11/29/2012 and the reply stated that Norton 360 should still be able to remove tracking cookies. WELL IT DOES NOT - WHAT HAS CHANGED FROM 16.0.2 TO 17.0 THAT WOULD CAUSE THIS. IS THIS A NEW BUG? The first reply did not answer my question however it was marked as "solved". I have rolled back to 16.0.2 and updated to 17.0 twice and the same thing has happened both times.

With firefox 17.0 Norton 360 does not pick up tracking cookies that were picked up with firefox 16.0.2. Uninstalled 17.0 and and reinstalled 16.0.2 - tracking cookies are picked up - updated to 17.0 and again no tracking cookies. I did not see anything in release note that would seem to reflect this situation. asked this question at 08:57 PST 11/29/2012 and the reply stated that Norton 360 should still be able to remove tracking cookies. WELL IT DOES NOT - WHAT HAS CHANGED FROM 16.0.2 TO 17.0 THAT WOULD CAUSE THIS. IS THIS A NEW BUG? The first reply did not answer my question however it was marked as "solved". I have rolled back to 16.0.2 and updated to 17.0 twice and the same thing has happened both times.

All Replies (1)

more options