> Not a big issue but it took me some time to realise it wasn't a problem with my bank's website.
Actually, it likely was. Your bank probably did not realize it but depended on some external component blocked by ghostery being loaded. I've seen the weirdest cases of this, such as one instance where a missing function in some javascript code was fixed for backwards compatibility in an ad-tag served by someone else...
So disabling the ad tag caused the site to fail with a javascript error.
In general, a banking website should work A-Ok with ads disabled and if it does not it is likely not Ghostery that is at fault but the bank (if only for not testing that their site works with ghostery or adblock installed).
I've also seen behavior like this with NoScript. Sometimes it's a total crap shoot as to which functionality works/doesn't work when you enable/disable certain scripts.
Actually, it likely was. Your bank probably did not realize it but depended on some external component blocked by ghostery being loaded. I've seen the weirdest cases of this, such as one instance where a missing function in some javascript code was fixed for backwards compatibility in an ad-tag served by someone else...
So disabling the ad tag caused the site to fail with a javascript error.
In general, a banking website should work A-Ok with ads disabled and if it does not it is likely not Ghostery that is at fault but the bank (if only for not testing that their site works with ghostery or adblock installed).