Hi everyone - I work for an ISV used by many large corporations and part of our solution includes a FF addin that has traditionally been deployed to users without their ability to control its behavior (i.e., can't remove, can't disable). Obviously, that direct functionality was removed in 40 and while most of our customers have remained on ESR 38, we've recommended CCK2 to workaround the issue for builds above.
As we approach ESR 45, the large enterprises that rely on us are again concerned about the distribution scenarios for enterprise plugins like ours. In the original bug thread, it was speculated that some solution would be devised prior to this ESR: https://bugzilla.mozilla.org/show_bug.cgi?id=1144127 Has an avenue been determined by which enterprises can safely/reliably deploy "forced" plugins for their users? We want to ensure we have compatibility with whatever approach at the time of its release. Thanks, Matt Matt Lavallee, Director of Product Management, Aternity Inc. 508.330.2100 (Mobile) [email protected]<mailto:[email protected]> www.aternity.com<http://www.aternity.com/>
_______________________________________________ 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"
