![]() Fine, or it would be fine, if I could force-enable the addon. You as a developer are then covered, but what about the end-users who want to use addons that are inconveniently unsigned? I was using Firegestures the other day, Firefox updated itself, and then suddenly Firegestures is disabled because it’s “unsigned”. ![]() You as a developer get an addon updated and signed within 1 hour. You stated earlier to an addon developer “just sign the addon” – and how long does signing an addon take? 1 month? 2 weeks? When happens when there is a security patch for the addon released? How long does that security patch take to become “signed”? What about beta versions of addons? Why should a developer be forced to sign his own addon, or those who want to beta-test it?īut alright let’s assume best case scenario. Either that, or you’re on Mozilla’s payroll. While it is easy enough to modify so that this is not the case anymore, it will likely irritate quite a few users and especially those who run unsigned add-ons in Firefox. It may come as a surprise to Firefox Nightly users that Mozilla set the default preference of the browser in regards to requiring signed add-ons to true. I HAVE 1PASSWORD 3.8.22 FOR MAC INSTALLYou will still get a warning message when you try to install unsigned add-ons, but the install button is there again so that it can be installed after all.Ĭaution: This site would like to install an unverified add-on in Nightly. You may install unsigned extensions again in Firefox once you have set the preference to false, a restart of the browser is not necessary. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |