> This is quite surprising as I have not seen this. I do get occasional dead > buttons due to all of the privacy add-ons I run, especially No-Script, but > also less intrusive ones like Privacy Badger.
> I have seen a few issues with sites taking advantage of some JS functions > outside of the standard that Chrome has added and Firefox has not yet > picked up. This is the fault of Chrome playing the old IE game of making > other browsers notwork correctly on some pages. I also have to fake the UI > identifier for some sites as they reject access from FreeBSD (Chase Bank, > I'm looking at you!) or do the wrong thing. > As regards chromium, I have deleted it it and will not consider ever using > it due to it's massive data collection and its blocking privacy tools like > No-Script. > Kevin Oberman, Part time kid herder and retired Network Engineer I know from experience what you mean with Chase Bank blocking online banking access if your user-agent string is not to the website server's liking. Chase Bank is not the only offender. Some websites, without blocking access, behave differently and wrongly depending on user-agent string. I got Chase Bank to work with an outdated version of Otter Browser and a fudged user agent. Sometimes it's not what browser you're using, but what browser the website software thinks you're using. I do find some scripts to cause problems and make some websites very slow. I had problems with Mozilla SeaMonkey on nfl.com when I was looking to see highlights on the last Super Bowl (last Sunday night). I was glad to close that browser window! Since this problem with Chase, using Mozilla Seamonkey under FreeBSD, affects me so directly, I could not resist making this response. Tom _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
