I'm looking into what we can do on the ESR.
Mike
On Wed, Nov 6, 2019 at 9:56 AM James Pearson
wrote:
> Is it likely that Mozilla will re-think this change as far as ESR is
> concerned?
>
> i.e. allow 'sideloading' of extensions in all future releases of ESR -
> potentially controlled via a
Is it likely that Mozilla will re-think this change as far as ESR is
concerned?
i.e. allow 'sideloading' of extensions in all future releases of ESR -
potentially controlled via a Policy ?
Thanks
James Pearson
Mike Kaply wrote:
You can deploy extensions as a part of Firefox by putting
to install
extensions as of today?
From: Enterprise On Behalf Of Mike Kaply
Sent: Friday, November 01, 2019 10:59 AM
To: Stephen Dowdy
Cc: Mozilla.org
Subject: Re: [Mozilla Enterprise] Mozilla To Stop Supporting Sideloaded
Extensions In Firefox
CAUTION
Marco Gaiarin wrote:
Mandi! Luca Olivetti
In chel di` si favelave...
I always put the extensions in the browser/extensions subdirectory where
firefox.exe is (some of them xpi, some of them unzipped), and, in my limited
testing, this still works with 68 esr (though when I create a user's
On 4.11.2019 1.30, Marco Gaiarin wrote:
Mandi! Mike Kaply
In chel di` si favelave...
The thing that is going away is the concept of sideloading where you put
extensions in a central location and they get loaded into Firefox and the user
can't remove them (they can only disable them).
But
Mandi! Luca Olivetti
In chel di` si favelave...
> I always put the extensions in the browser/extensions subdirectory where
> firefox.exe is (some of them xpi, some of them unzipped), and, in my limited
> testing, this still works with 68 esr (though when I create a user's profile
> I set
Mandi! James M. Pulver
In chel di` si favelave...
> > Also, if we have to switch to policy, please have the
> > distribution/policies.json
> > to be non-monolithic: have a single file is a bit rigid nowadays, where
> > modern configuration files work on split-files.
> >
> > Eg, make the
El 4/11/19 a les 16:12, James Pearson ha escrit:
P.S. I'm still a bit confused about 'sideloading' - as the Blog post
says the change will be with Firefox 73/74 - but I can't seem to enable
'sideloading' with ESR 68 - i.e. want to be able to load named
extensions from a central location
Maybe "deployment" is easier in some sense, but the massive change
introduced by Quantum, which annihilated a large number of add-ons, has
made it impossible to return to Firefox's previous functionality and
usability (esp. the user interface). Thus the new state of affairs is
that, although it's
I'm guessing if you're deploying policies as policies.json you probably
can template it in your configuration management tool. I find this is
where erb templates shine in puppet for instance.
--
James Pulver
CLASSE Computer Group
Cornell University
On 11/4/19 6:30 AM, Marco Gaiarin wrote:
>
Marco Gaiarin wrote:
The thing that is going away is the concept of sideloading where you put
extensions in a central location and they get loaded into Firefox and the user
can't remove them (they can only disable them).
You will still be able to put extensions into distribution/extensions
Mandi! Mike Kaply
In chel di` si favelave...
> The thing that is going away is the concept of sideloading where you put
> extensions in a central location and they get loaded into Firefox and the user
> can't remove them (they can only disable them).
> You will still be able to put extensions
Hello,
> However, what policy settings do I need to have an arbitrary extension
> enabled by default for all users?
>
> I've put the extensions in distribution/extensions - but they don't
> appear in the extensions list when running Firefox
XPI packages placed under distribution/extensions are
El 1/11/19 a les 16:59, Mike Kaply ha escrit:
You will still be able to put extensions into distribution/extensions
because they simply get installed into Firefox as normal extensions.
I still prefer browser/extensions, this way users cannot mess up with
the extensions I preinstall.
I don't
As I just happen to setting up ESR 68 (on Linux) with a couple of third
party extensions that I want to be loaded by default - this thread is
rather timely ...
However, what policy settings do I need to have an arbitrary extension
enabled by default for all users?
I've put the extensions in
Hello,
> To clarify, loading them directly into /extensions is
> going away, and the "as normal extensions" deployment means loading into
> distribution/extensions, where they are copied into and then run from
> the user profile?
If I understand the blog post correctly, it is "yes".
As the
>
> The thing that is going away is the concept of sideloading where you put
> extensions in a central location and they get loaded into Firefox and the
> user can't remove them (they can only disable them).
> You will still be able to put extensions into distribution/extensions
> because they
On Fri, Nov 1, 2019 at 10:39 AM Stephen Dowdy wrote:
> On 11/1/19 9:21 AM, Mike Kaply wrote:
> > You can deploy extensions as a part of Firefox by putting them in the
> distribution/extensions directory and then locking them via policy.
> >
> > This has always been a better way then putting them
We also struggled with the switch from cck to GPO, but 2 weeks ago we
succesfully deployed Firefox 68. The GPO does what we need although it
feels cck gave more control, since you could add your own preferences,
which does not seem possible with gpo.
During testfase we encountered a problem with
On 11/1/19 9:21 AM, Mike Kaply wrote:
You can deploy extensions as a part of Firefox by putting them in the
distribution/extensions directory and then locking them via policy.
This has always been a better way then putting them in system directories where
they might not get updated properly.
You can deploy extensions as a part of Firefox by putting them in the
distribution/extensions directory and then locking them via policy.
This has always been a better way then putting them in system directories
where they might not get updated properly.
Mike
On Fri, Nov 1, 2019 at 8:47 AM Luca
El 1/11/19 a les 14:26, Mike Kaply ha escrit:
This method was deprecated by Chrome years ago and we provide new and
better methods via policy.
If I wanted to deploy chrome I would be deploying chrome. Maybe it would
spare me a lot of headaches.
As it stands today, any extension installed
This method was deprecated by Chrome years ago and we provide new and
better methods via policy.
As it stands today, any extension installed by these mechanisms gets
disabled anyway.
And we've actually made deployment easier with each release.
Mike
On Fri, Nov 1, 2019 at 8:18 AM Luca
https://news.slashdot.org/story/19/11/01/0331216/mozilla-to-stop-supporting-sideloaded-extensions-in-firefox
Really?
If so, thank you (not!) for making deployment more difficult with each
release.
Bye
--
Luca Olivetti
Wetron Automation Technology http://www.wetron.es/
Tel. +34 93 5883004
24 matches
Mail list logo
