[EddyHaskel]

I am careful about which domains are allowed to process javascript via my browser.
Of course I whitelist bridgebase.com as always trusted.
But starting on March 14, I can no longer log in on "V3," the html browswer "newest" version.
It times out and thinks I am not connected to the internet.
This is a classic sign that one or more domains requesting javascript access are not getting it.
I look at the domains that would automatically have javascript privs on login if I allowed all, and that list is extensive -- at least 19 domains other than bridgebase.com are trying to write javascript when I attempt to log in.

I need to know which of them are required in order to log using BBO v3 in via my browser (Firefox 74.0 16bit) so I can allow them without allowing all.

Interestingly, I CAN still log in using the old windows client. I have been trying hard to adapt to the new "V3" (it hasn't been easy), forcing myself to keep using it even though many of the things we all loved about the old Windows client have disappeared. But that's fodder for a different forum entry.

Please tell me which domains now require javascript access so I can allow them by choice.

Thanks!

[barmar]

EddyHaskel, on 2020-March-14, 14:44, said:

IPlease tell me which domains now require javascript access so I can allow them by choice.

We haven't changed that, it's still bridgebase.com for the BBO functionality.

However, we also display ads, and they come from many other domains that are out of our control.

[EddyHaskel]

barmar,
Thanks for quick reply!
It's back up and running; and you are right -- allowing only bridgebase.com is the only javascript needed for the site to function.

In the intervening minutes I tried a couple experiments....
Here is what worked:
- deleted all BBO related cookies and browser site data;
- turned enhanced tracking ON (previously I had an exception for bridgebase.com);
- closed and reopened the BBO tab with new settings, and voila!

Maybe I had some old cookie that stopped working properly or something.
Or, maybe because I was not allowing any of the tracking sites to use javascript while "allowing" bridgebase.com to track caused a problem.

In any case, all settled now.

Many thanks,
Dave/Eddy

[Gerardo]

The servers managing v3 connections were overloaded.

We added more servers, and upgrade the existing ones.