Firefox 42 will not allow unsigned extensions
wiki.mozilla.org
Firefox 42 will not allow unsigned extensions
1–10 of 315 posts
Re: Firefox 42 will not allow unsigned extensions
#2The assumption being that developers need to test as they develop. And are a more informed user.
Re: Firefox 42 will not allow unsigned extensions
#3It's important to note that the Developers Editions (and the Nightlys) will have a setting for disabling the requirement. The assumption being that developers need to test as they develop. And are a more informed user.
Re: Firefox 42 will not allow unsigned extensions
#4It's important to note that the Developers Editions (and the Nightlys) will have a setting for disabling the requirement. The assumption being that developers need to test as they develop. And are a more informed user.
Re: Firefox 42 will not allow unsigned extensions
#5It's important to note that the Developers Editions (and the Nightlys) will have a setting for disabling the requirement. The assumption being that developers need to test as they develop. And are a more informed user.
Did they say why beta wouldn't have this setting? If anything beta is closer to release and developer would target that. Developer edition is still nightly if I'm not correct?
"There will also be special unbranded versions of Release and Beta that will have this setting, so that add-on developers can work on their add-ons without having to sign every build."
Re: Firefox 42 will not allow unsigned extensions
#6Re: Firefox 42 will not allow unsigned extensions
#7It's important to note that the Developers Editions (and the Nightlys) will have a setting for disabling the requirement. The assumption being that developers need to test as they develop. And are a more informed user.
(In addition to people always being able to recompile the browser with whatever modifications they want, of course.)
Re: Firefox 42 will not allow unsigned extensions
#8What is the point of this? Shouldn't users be allowed to make their own decisions no matter how stupid or dangerous?
The issue is that most users don't understand software on a deep level, and just click "yes" on dialog boxes, etc.
It does make sense to keep the defaults where it prevents most users from harm.
Re: Firefox 42 will not allow unsigned extensions
#9Now, let's just hope that the other side of the coin is a concern for API backward compatibility, so that people don't need nightly versions of addons and a developer edition to keep their addons in a usable state...
Re: Firefox 42 will not allow unsigned extensions
#10What is the point of this? Shouldn't users be allowed to make their own decisions no matter how stupid or dangerous?