Browser extension conflicts: How to diagnose and resolve them
Browser extensions often do conflict with our site code at Daily Kos for various unavoidable reasons.
The extensions most likely to cause problems are adblockers and third-party tracking blockers. At times, extensions update silently, meaning that extensions formerly coexisting comfortably with our site code may suddenly become incompatible. Unfortunately, it can happen the other way, too--one of our site updates can abruptly run afoul of a previously-unproblematic extension. And then, most annoying of all, we can have a cache issue occurring at the same time as an extension issue.
The most reliable way to diagnose the interference from extensions is to open a private or incognito window on your browser, then load the site. If you're following a link from of one of our emails to the site, you'll want to log into your email in a private/incognito tab and then proceed as you usually would from there.
Private/incognito mode typically disables extensions. So, if you see expected behavior on a private/incognito window it strongly suggests the presence of a conflicting extension. That's helpful information, but your work isn't yet done. The next step is to go through yours by trial and error to determine the cause(s) and determining which, if any, you'd like to disable for our site.
Before you try that step, however, you may want to check whether you have an Avast or Brave browser, or any other browser that promotes itself as having extra privacy protections built in. The highest privacy settings on Firefox can also be problematic.
If your browser builds those blocks into their base design, so that it is not possible to adjust your privacy setting, then the private/incognito mode option won't help you much as a diagnostic. Trying a different browser would consequently be the test case; switching browsers has been the solution that some other users in that situation have adopted.