![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
ZDNet Comments no longer open in Firefox, but do in Chrome or Bing. What's the problem here?
Clicking on the Comments section in any ZDNet article (https://www.zdnet.com/article/) gets no response at all. The Comments section doesn't open, I'm not prompted to log in -- nothing. The cursor does change from the default arrow to a hand with pointed finger, as usual, and the Comments bar color flashes as it should when I click on it -- but that's the limit of interaction. I've tested the link with Chrome and Bing and the function still works there, but not in Firefox, and apparently hasn't since about the 26th of July. What's going on, and how can this problem be addressed?
Gekose oplossing
Make sure you are not blocking content.
Diagnose Firefox issues using Troubleshoot(Safe) Mode {web link}
A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there?
https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop
Many site issues can be caused by corrupt cookies or cache.
Warning ! ! This will log you out of sites you're logged in to. You may also lose any settings for that website.
- How to clear the Firefox cache {web link}
All Replies (4)
Gekose oplossing
Make sure you are not blocking content.
Diagnose Firefox issues using Troubleshoot(Safe) Mode {web link}
A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there?
https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop
Many site issues can be caused by corrupt cookies or cache.
Warning ! ! This will log you out of sites you're logged in to. You may also lose any settings for that website.
- How to clear the Firefox cache {web link}
Allowing trackers through the ZDNet video page allowed me to view the videos. But the failure to allow me to access comments or sign in cleared up spontaneously; I took no action here, but functionality was restored as before. No explanation, no obvious reason for it to happen. Except I had remarked to ZDNet through their Google-operated help facility that the problem existed. I will continue to keep an eye on it. Thanks, Fred, for your advice and insight. You helped me resolve what part of my problem remained unresolved.
It's possible they checked the website and tweaked something.
My thought precisely. It bothers me that they didn't catch this upon installation of whatever change they internally approved, but if we keep them honest this might not happen as often. Let us hope.