Isn't this cat-and-mouse issue between extension vetting and new Firefox versions always present when running Firefox beta? I assumed it was one of the tradeoffs, i.e., parts may be broken...?
No. This is a new feature that disables all unsigned extensions. It will be in the next version of the normal Firefox. The setting to allow unsigned extensions will be removed in the version after that (or so I've read).
Chrome has done something similar for a few years now, but (unlike Firefox) Chrome allows white-listing extensions via Group Policy.
Comments
Isn't this cat-and-mouse issue between extension vetting and new Firefox versions always present when running Firefox beta? I assumed it was one of the tradeoffs, i.e., parts may be broken...?
No. This is a new feature that disables all unsigned extensions. It will be in the next version of the normal Firefox. The setting to allow unsigned extensions will be removed in the version after that (or so I've read).
Chrome has done something similar for a few years now, but (unlike Firefox) Chrome allows white-listing extensions via Group Policy.