4 ms·
While annoying I see the benefit as a user and addon developer. It protects less sophisticated users from abuse. Though I do prefer Chrome's opt in to a dev mod
by paulryanrogers 6y ago
While annoying I see the benefit as a user and addon developer. It protects less sophisticated users from abuse. Though I do prefer Chrome's opt in to a dev mode without a whole separate binary.
- alphabet9000 6y agothere are examples of firefox protecting 'less sophisticated' users from abuse while still allowing them to go through with it if they really want to. such as, opening up the inspect element area and receiving a warning + having to type 'allow paste' to be able to paste javascript into the console. there's ulterior motives for requiring mozilla to sign extensions, and it isn't about protecting users.
- paulryanrogers 6y agoWel one can go to about: debugging and load unsigned add-ons from there. It's just temporary. Edit: Forgot to mention you can also self host extensions once they get signed. Chrome does not allow this, or at least not without group policy.