Этот сайт имеет ограниченную функциональность, пока мы проводим техническое обслуживание для улучшения его работы. Если какая-либо статья не решила вашу проблему и вы хотите задать вопрос, наше сообщество поддержки ждёт вас: @FirefoxSupport в Твиттере и /r/firefox на Reddit.

Avatar for Username

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

Эта тема была архивирована. Если вам нужна помощь, задайте новый вопрос.

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

  • 1 ответ
  • 1 имеет эту проблему
  • 5 просмотров
  • Последний ответ от the-edmeister

DougHoward
DougHoward
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.

Все ответы (1)

the-edmeister
the-edmeister
  • Moderator
more options

Locking as a duplicate thread.

https://support.mozilla.org/en-US/questions/943027?esab=a&s=&r=1&as=s