Open seniordevel opened 6 months ago
This setting once was disabled by Mozilla. For details see: https://support.mozilla.org/en-US/questions/1148149
Why reenable this setting?
Currently it is impossible to install addons lacking of correct Mozilla signing.
This affects
...as well as...
Currently the overall Mozilla signing process is hell. For "sparetime developers" the process is simply much too much effort.
For me, the signing process makes sense when you want to publish a working addon, but not while initial development and testing is in progress.
For safety and security reasons, restrict it to local xpi files, opened from addon manager.
An example for needed code modifications can be found here at Github:
Firefox fork 'Floorp browser' https://github.com/Floorp-Projects/Floorp
This setting once was disabled by Mozilla. For details see: https://support.mozilla.org/en-US/questions/1148149
Why reenable this setting?
Currently it is impossible to install addons lacking of correct Mozilla signing.
This affects
...as well as...
Currently the overall Mozilla signing process is hell. For "sparetime developers" the process is simply much too much effort.
For me, the signing process makes sense when you want to publish a working addon, but not while initial development and testing is in progress.
For safety and security reasons, restrict it to local xpi files, opened from addon manager.