Re: sane chromium default flags - include --enable-remote-extensions
- Date: Sat, 25 Feb 2017 15:41:58 +0300
- From: Konstantin Khomoutov <flatworm@xxxxxxxxxxxxxxxxxxxxx>
- Subject: Re: sane chromium default flags - include --enable-remote-extensions
On Fri, 24 Feb 2017 15:14:18 +0100
md@xxxxxxxx (Marco d'Itri) wrote:
> > To be honest I've the feeling that we're doing a disservice to our
> > users when we release stretch with the current defaults. Putting
> I amazed by this decision: this is the kind of thing that makes
> people not take Debian seriously.
> This behaviour should either be implemented consistently by all
> browsers or the default reverted.
> Users expect their browser to update the extensions that they have
> installed themselves, so the excuse about "unrequested network
> connections" looks like just an ideological decision.
It's not even about updating: the first version of chromium with this
build-time tweak simply disabled all already installed extensions for me
so they were not activated when I restarted chromium after that upgrade
session -- and hence were not shown in UI etc.
What's worse, it's futile to attemt to reinstall them: the settings tab
for the extensions works OK, the chromiums "extensions store" (whatever
its real name is, I dunno) works OK, just when you try to install an
extension, you get some mystical error message having nothing to do
with what Debian's build did, and with no hint at what to do next.
I possess the necessary google-fu and I'm a programmer after all, so
that wasn't too hard for me to find the cause and implement the
solution, but for a plain computer user that would be a complete