Summary of Issue: A user (HorridModz) is experiencing an issue accessing discuss.python.org on their Windows 11 device using Microsoft Edge. The issue causes the site to be impossible to interact with, with buttons and scroll bars not loading properly.
Initial Theory: The issue was initially thought to be caused by a cookie (discuss.python.org > Service Workers > https://discuss.python.org/) and not by any browser extensions. However, further testing revealed that the issue does not occur in Microsoft Edge’s Incognito Mode or when all extensions are manually disabled.
Culprit Extension: After manual testing, the culprit extension was found to be the Scrollbar Customizer extension. The user had to disable it to resolve the issue.
Follow-up Action: sam has emailed the developer of the Scrollbar Customizer extension to report the issue.
I originally posted this here, but was told that this issue should be reposted on this site.
On my computer, I am not able to access this website. I am posting this here via my phone. I have opened an issue on github documenting this phenomenon. Please read the issue: Can't Access discuss.python.org · Issue #106841 · python/cpython · GitHub Make sure to scroll down and read the entire thing.
Though you should still read the github issue, here is a summary.
Does the same happens in an incognito tab in the same browser or in another browser on the same device?
No, this does not happen in Microsoft Edge’s Incognito Mode.
I only have Microsoft Edge installed due to my laptop’s incredibly low storage space, but I will test in another browser when I get a chance (it’s a pain to set up). That should be tomorrow.
That usually means an addon is involved. Do you have the YouTube AutoQuality one installed? If not I’m afraid you will need to uninstall one by one to find the culprit.
I’m sorry, it looks like the problem is from an extension after all! I have a browser extension that disables all other extensions, which is what I used to “disable” all my extensions during my initial testing. But I guess that it wasn’t completely disabling them, because upon manually disabling all my extensions, the problem went away!
I will work on discovering the culprit extension right now. And I’ve learned my lesson - never rely on third-party tools; always do stuff the manual way if you need to test something.
The culprit was the Scrollbar Customizer extension. I have never had issues with it for any other site, so this is weird. I guess I’m forced to disable it - I’ll miss you, Scrollbar Customizer 
I shot off an email to the dev just in case