https://bugzilla.mozilla.org/show_bug.cgi?id=1255039 and dependent bugs implemented a way in which addons.mozilla.org is able to gather data about extensions the user has installed (and be it just a "yes/no"). We don't want this.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
FWIW: I pondered quite a while whether we should disable this API for both chrome and content but finally opted for doing so just for the latter. There might be breakage involved (especially in the longer run) by not allowing Firefox internals to use it. However, I am not sold to this. Thus, if there are good arguments for kicking window.navigator.AddonManager fully out let me know and we can reconsider it.
Trac: Status: assigned to needs_review Keywords: TorBrowserTeam201705 deleted, TorBrowserTeam201705R added
r=mcs
Looks good to me, and the approach seems sound as well.
My only nit is that in the commit message you should s/Priviledged/Privileged/ (remove the extra 'd').
Thanks. Fixed and applied to tor-browser-52.1.1esr-7.0-1 and tor-browser-52.1.0esr-7.0-2 (commit 9de9d5a74472423e5a7e5754f5d93b2d89103dfe and e5da14c4ae6e3917928b3004bca7bd49e972089e).
Trac: Resolution: N/Ato fixed Status: needs_review to closed