While we appreciate the reports (and understand your frustration), its much harder for us to track, assist and test the issues you’re experiencing if they’re all rammed into one thread. In this thread, you’ve had 3-4 separate issues – none of which follow the template that we use to get the most accurate information surrounding the issue, and tell us exactly how to reproduce it on our end.
In fact, I was scrolling up so that I could give you one sweeping list of answers to each of your questions, but there are quite literally too many to keep track of. I would very much like to assist you with the issues you’re encountering, but we need to take them one at a time – or at the very least address them one per thread.
Additionally, if you happen upon a site that isn’t working properly, instead of testing in Chrome, you should simply lower your Shields in the Shields panel and see if the site works. If it does, then that means one of the protections in Shields is blocking something that the site requires to run/function as intended (which we can figure out and address). If it does not, then that points to something in the browser specifically causing the problem.
When you see this behavior, note that in your Shields panel now (w/Shields = down), you’ll notice the
Report a broken site button – please use this so that we can see the sites that are in conflict with the browser without you (or other users) having to report it.
Please understand that support team (and the team in general) is small and we have thousands of threads/tickets/cases/[support] requests to respond to on any given day. We will always do our best to ensure we respond to and resolve as many issues as possible, but hope you understand that there are limitations beyond our control at this time.