4 ms·
Then disable it by default. Don't show non-WebEx addons in the mozilla website. If a user tries to enable it, put up a big red warning sign saying how dangerous
by andrepd 9y ago
Then disable it by default. Don't show non-WebEx addons in the mozilla website. If a user tries to enable it, put up a big red warning sign saying how dangerous it is and a checkbox saying "I understand". But in the end, let the users do what they want.
This way 99% of the users will never use unsafe addons, the 99% who won't even miss them. But power user who understand and want to, let them ultimately have the freedom to do "stupid" things (what you consider as stupid).
- Animats 9y agoThe underlying XUL machinery that XUL-type add-ons access is going away. It's never been there in mobile Firefox. That's why they have to go. Whether Firefox add-ons should be restricted to what Google Chrome supports is another issue.
- yoasif_ 9y ago> Whether Firefox add-ons should be restricted to what Google Chrome supports is another issue. It's not, though. See: https://discourse.mozilla.org/t/support-ublock-origin/6746/451 https://discourse.mozilla.org/t/support-ublock-origin/6746/4...
- kuschku 9y agoThis is not a security question, but a performance and safety question. Many of the major performance improvements in Chrome were possible because the extensions were decoupled from the browser itself. If Firefox ever wants to improve its performance, it can not keep running XUL extensions anymore.