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 by these mechanisms gets disabled anyway.

And we've actually made deployment easier with each release.

Not really if you remove facilities that have been working since day one (I've been deploying mozilla since it was a monolithic application, and I preferred it that way, just one application to deploy instead of two that have a lot of overlap). Maybe I wasn't using a "sanctioned" method to to the deployment, but that was just because there was *no* method to do it when I started doing it, hence, with each new release, I had to jump through hoops to keep it working. Anyway, the "new", "improved" methods are less straightforward than the old fashioned ones.

Bye

--
Luca Olivetti
Wetron Automation Technology http://www.wetron.es/
Tel. +34 93 5883004 (Ext.3010)  Fax +34 93 5883007
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise

To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise 
or send an email to [email protected] with a subject of 
"unsubscribe"

Reply via email to