7/21/2023 0 Comments Qupzilla addonsBut where is the rational justification for destroying what FF has always been and what drew us all to it – a framework for security and functional customization. It is fine to overlay simplification for the inexperienced. 0.8, live in the browser, and am despondent and filled with frustration at the loss of productivity that is being forced on the base of serious users day by day. It should be added that I migrated to FF from Netscape 3 or 4 at around v. I know it’s probably already way too late but please, stop ruining my favorite browser. Except when people want that, why go for a knockoff? You throw up Google-like roadblocks and provide Google-quality APIs, you’re going to get the same kinds of crap that already litters the Play Store. Anyone who has the kinds of ideas that made Firefox extensions the killer app they once were is long gone. I’m sure there will be another bad idea to alienate developers and vast swaths of your user base soon enough.ĪMO is already fast becoming another app store-like junkyard with useless brand apps and badly-written niche trinkets. Please, for the love of all that is holy, let this one drop. Nobody asked for this, nobody can justify it beyond Mozilla’s standard catch-all (“because this is what Google is doing”) and it’s clear it’s more trouble than was anticipated. You’re making Firefox less secure by “making Firefox more secure.” ![]() This is going to result in a lot of technical users not updating their browsers. What have the solution for the authors not-restartless-addons? > temporarily loading unsigned restartless add-ons Why remove the toggle at all? It seems like something users would want. If you take away this option, there are 3 other browsers installed on my machine, and guess what? See ya, FireFox. It’s a bit high-handed to remove the option entirely. It’s enough of a PITA to change the about:config setting, and it’s necessary for those addons that haven’t been bothered to update yet still provide lots of value (e.g. If we want to install them, you shouldn’t prevent us from doing so. Signing will be mandatory in the beta and release versions of Firefox from 46 onwards, at which point unbranded builds based on beta and release will be provided for testing.Ĭategories: developers, releases 119 responses ![]() The updated timeline is available on the signing wiki, and you can look up release dates for Firefox versions on the releases wiki. We also want to ensure that developers have adequate time to finish the transition to signed add-ons. ![]() We are delaying the removal of this preference to Firefox 46 for a couple of reasons: We’re adding a feature in Firefox 45 that allows temporarily loading unsigned restartless add-ons in release, which will allow developers of those add-ons to use Firefox for testing, and we’d like this option to be available when we remove the preference. This requirement can be disabled by toggling a preference that was originally scheduled to be removed in Firefox 44 for release and beta versions (this preference will continue to be available in the Nightly, Developer, and ESR Editions of Firefox for the foreseeable future). In Firefox 43, we made it a default requirement for add-ons to be signed.
0 Comments
Leave a Reply. |