Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 3 Feb 2020 17:39:36 -0800
From:      Kevin Oberman <rkoberman@gmail.com>
To:        Dave Horsfall <dave@horsfall.org>
Cc:        FreeBSD Ports <freebsd-ports@freebsd.org>
Subject:   Re: xterm-353
Message-ID:  <CAN6yY1viKMHtn855E00dz3WnzrBBDU30iZ69aqsQG0Ps384UiA@mail.gmail.com>
In-Reply-To: <alpine.BSF.2.21.9999.2002040632440.33501@aneurin.horsfall.org>
References:  <20200202103600.1959de17@dismail.de> <20200202154227.GB1309@albert.catwhisker.org> <20200202121118.71446c54@dismail.de> <20200202123845.46fc2d8b@dismail.de> <20200202185446.GB60645@server.rulingia.com> <20200202205050.GA2182@squirrel.exwg.net> <600545092.3036828.1580684357864.JavaMail.zimbra@his.com> <20200203075041.GA2321@squirrel.exwg.net> <alpine.BSF.2.21.9999.2002040632440.33501@aneurin.horsfall.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Mon, Feb 3, 2020 at 11:38 AM Dave Horsfall <dave@horsfall.org> wrote:

> On Mon, 3 Feb 2020, Christoph Moench-Tegeder wrote:
>
> > You're right. For some reason, firefox is not handling the additional
> > compression correctly (I see Content-Encoding: gzip in the headers, so
> > it's advertised, but not unzipped by the browser, so I get a double-
> > compressed file. Oh tempora, oh mores). Not enough time to dig into that
> > right now.
>
> FWIW, I find that Firefox is becoming increasingly unreliable, with "dead"
> buttons etc (yes, I have JS enabled against my better judgement) and have
> to use Safari/Chrome instead.  This is a pity, as I find that FF is much
> faster and I've used it for many years.
>
> -- Dave
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1viKMHtn855E00dz3WnzrBBDU30iZ69aqsQG0Ps384UiA>