-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Report Broken Add-Ons Here: Sensible default addons list #63
Comments
I think that is a good idea! |
I installed all addons in the default list. The only one that doesn't install at all is MYKI Password Manager. That's a lot better than I expected. How many of the other ones actually work is a different thing I didn't get around to test so far. |
Yeah, we can pare down that list if things just plain don't install. I threw MYKI off the list. If we had something on the add on manager screen pointing to docs about how to set up your own collection, and made it easy, we could pare down the list to the ones that really work, and let people set their own list if they want to play with broken ones (or, say, are those add-ons' devs). |
Should we rename this to "Please report broken add-ons here" and sticky it? I've seen a few posts in other issues where people reported broken issues. |
That would make sense. I didn't know we could sticky issues.
|
History Block ( https://addons.mozilla.org/en-US/firefox/addon/historyblock/ ) can be installed, the settings screen can be opened, but new domains can't be added and import also does not work, the list of the blocked domains just stays empty. |
tabliss is not working. |
I've pulled Tabliss because it doesn't seem able to take over the new tab page. History Block I am going to leave for now; that sounds like a bug the add on devs might be able to fix. |
Tabliss will never work if the intention of that add-on is to modify the new tab page. The new tab page is not part of the browser engine but rather a native android screen. A lot of add-ons will not work in Fenix due to this reason. Things like themes, and a lot of about:config settings that affect parts of the browser that is no longer governed by the browser engine will not work. Changes to the new tab screen can only be done by modifying the app, and likewise any potential themes can only be created by adding appropriate resources and modifying the app, for example. |
Cookie AutoDelete may cause that app crash after browsing a webpage a few seconds later. |
https://github.com/mikecrittenden/shortkeys |
Question:Could someone add this to the repo and link to it in the .github/ISSUE_TEMPLATE/addons-request.md
|
@baopaau |
Buster: Captcha Solver for Humans doesn't work on v1.4.0. I can't even install it, it says "Failed to install Buster: Captcha Solver for Humans". |
@mfymn I can reproduce this. I've taken Buster off the list. |
universall bypass doesn't work on v1.6.0 |
imtranslator can be installed but doesn't work on v1.6.0 |
cookie quick manager also doesn't work on v1.6.0 |
SoundCloud Downloader (https://addons.mozilla.org/id/android/addon/soundcloud-dl/) can be installed but doesnt download songs / album. instead, it stuck on full bar and never do anything. tested with v1.7.1 |
video downloadhelper cannot be downloaded at version 1.7.1 |
im translator still doesn't work on version 1.7.1 |
Search by Image the popup windows sometime cannot appear or when trying to search image its just back to current page IceRaven Version 1.10.0 |
video downloadhelper cannot be downloaded at version 1.10.1 |
Multi Container extension(by Mozilla) doesn't work well. almost unusable :(( |
video downloadhelper cannot be downloaded at version 1.11.1 |
FYI: FireMonkey – Extension for 🦊 Firefox mentioned above was not found in the collection group |
Yes. It is by debating and discussing that we reach a consensus. I understand that there are some extensions with important features that don't currently exist, natively in FF and in any other Android browser, but using extensions that haven't been updated since at least January 2021 is being kind of negligent. , because many of them are from the time when the old Fennec project was used, where it made sense to use them and that they were suitable for mobile, with the current API, which is no longer used in the PC version and that some developers already stated this clearly in their descriptions of their respective extensions, which are difficult to implement in the current FF for Android.
A feature like this is interesting and cool, but it would be better to use it with a recently updated extension.
Extensions that are not being updated regularly with a minimum period of 3 months and a maximum period of 6 months (at least at my discretion) from the last update released, should not be recommended to be used. Iceraven, in this issue is: 'Report broken add-ons here: sensible default add-on list'. This already shows what I mean.
Just gather a lot of people and create a discussion in the repository mozilla-mobile/fenix and don't stop charging for action on the part of those responsible for the Fenix project.
It's like the saying goes: "One swallow doesn't make a summer."
Often, it may be that the developer of the extension itself has not released its source code for others to fork, or does not have developers experienced in this type of subject.
That's the problem, who will put themselves ahead of this enterprise? Even I could change my concept, but I would have to see concrete results in practice.
I don't like it either, but seeing extensions of "Fennec" time, it's hard to support such a thing. Options may even have it, just look for it. Otherwise, it's better to go without some specific features than to possibly be invaded by a serious extension flaw that could lead to malware or spyware.
Is it the same as eliminating resources? Not. It is one thing to take an important native resource and delete it where you should never do, another thing is to take an extension that many times may not have been made to the platform it was intended for and can get broken and not work properly.
Yes, it's an interesting feature, and I saw that this extension is open source which is a great sign, too bad it hasn't been updated in a long time and in the description it says: "Using this extension, it is possible to clear cookies from three different zones:
Definitions: And how come extensions like 'I don't care about cookies', 'Cookie AutoDelete' and 'Cookies Manager' haven't implemented this feature yet? Are they unaware of such a feature? Could it be that by making a request to each of them, they could not implement it? There are several possible questions.
Yes, I agree that some extensions don't do what others do. Just because such an extension doesn't have such a feature doesn't mean it can be implemented later.
It would be better to use these extensions you described in the form of scripts placed in FireMonkey, Greasemonkey, ViolentMonkey or TamperMonkey.
Yes. But why keep without updating it, it makes no sense. It's better to get rid of it once and for all and continue with the development of the Privacy Badger, which will soon be another one that will seem to be abandoned.
It's not because they requested that they should be fully placed, it would have to do long tests and see if they really suit Mobile as SingleFile that works very well both on Desktop and on FF Android and is recently updated.
Yes, that's why there are also Fennec F-Droid forks that say "Fennec" but only in the name of the old project and the Mull Browser, it has no conditions to access extensions but also access to about:config with little limitation.
Right. Why am I going to install an extension that doesn't work or is partially functional. If it works great, cool. Now, it works broken, with grotesque errors, it has to be discarded yes, like Flagfox and ImTranslator that are broken and that were not even made to support FF Android, let alone forks.
Yes, unfortunately many extensions have been blocked, I created a discussion 1 year ago and believe that they have not responded so far, and if more people show up, it would be ok to do a vote on which extensions work properly for Mobile, now in relation to low market share is that the Mozilla Corporation, in a short time, lives on revamping the visual aspect of the browser
In a way, providing up-to-date extensions: yes, outdated: no. I don't agree with this, because from the moment someone requested the inclusion of such an outdated extension, they are wrong with the request they made. Because it has to see in her description if there is compatibility support for the current API used in Android and if this extension has regular updates.
I agree. If they don't work for anyone, there's no need for them to be on the list, especially if you have any that may contain malware or spyware. |
I agree, but to my knowledge no one has created a new extension with that functionality or updated an existing extension to add that functionality. In the absence of either of those things, the choice is to use the non-updated extension, or to lose the feature completely. By including the extension in the list of available extensions, Iceraven is giving users the option to use it. They also have the option not to use it for security or other reasons. If someone wants to develop a new extension that does what that one does, and update it regularly, that would be great. I'm sure we could get that swapped in for the one we're using on the default list if it popped into existence. But no one has shown a willingness to do that. It's sometimes very hard to get people to work on open-source projects for free. The Iceraven project iself (Not extensions, the core project) has been looking for volunteers to help interfect out for some time now, and hasn't gotten any takers. In the absence of a) Mozilla incorporating things like this into it's upstream browser, b) Someone volunteering to code it for Iceraven, c) Creating a new extension/updating an existing one to add the new functionality in a more up to date implementation; there is going to be some reliance on the part of some users on old extensions like this one. Their availability is actually what draws a lot of users to Iceraven.
I think you're going to have rough sledding getting that sort of standard adopted in a browser that came into being in part to let people use old extensions. Implementing a rule like that would probably cause half the user base to bolt instantly unless of course a vibrant ecosystem of regularly updated extensions could be created to replace the old ones, but people would need to create and update them and no one is stepping up.
I'm, seemingly permanently, banned from that repo (Long story). I would imagine I'm not the only one. If you or someone else wants to go over there and make a bunch of feature requests, that's up to you. It's outside the realm of what they will allow me to do personally. I think it's also worth noting that even before being banned there, when I would make a simple request, it went something like this: Still open, two years later. Someone submitted a patch to them to add the feature, they rejected it. It was one of the first patches incorporated into Iceraven and works well to this day. I don't think it's so much that Mozilla hasn't heard these type of ideas as that their target demographic for their browser isn't people who want them. They have a different vision. That's implicitly why a lot of the forks that exist exist, to cater to groups that Mozilla isn't catering to with their main Firefox project, while incorporating the Mozilla code and updates that they need to in order to keep projects viable.
Broken, not simply not updated recently.
I agree that it'd be nice if the Mozilla folks implemented those things in Firefox, which eventually we would also get downstream in Iceraven. However, the Mozilla folks aren't implementing them. They've been suggested, the Mozilla folks either don't want to implement them, are divided on whether to implement them or not, or have other priorities. It'd be cool if Iceraven implemented them itself, but we're down to one developer right now (We used to have three) and he's been pretty clear that he doesn't want to devote the extra time to do expansive stuff like that right now. He's not against adopting features like that, he's just not personally going to do them (Keep in mind he's working for free and has a day job that isn't this.). He'd happy to have a volunteer to do it, though. Go find him one or more people if you can. I've tried and failed to find them. |
@bonyjose, the problem with the extension being broken for so long is her own, and it's not Iceraven's in itself. In this case, you would have to contact the developer of the extension and see if it will provide proper support to use it in the FF version for Android. |
@bonyjose just use NewPipe app. for downloads. |
Please await |
Sponsorblock not in the list of addons after version 1.13.0. Installed in this version, works fine in version 1.17.0 but doesn't show up in the search list. |
Hello, |
Multi Account Containers is mostly unusable. |
I suggest to open another seperate thread for new-addon-requests. Would be easier to find IceRaven related issues. |
Hello, I got "Failed to install Violentmonkey" on v2.1.0, thanks. |
Floccus Bookmark Syncy addon not working. I cant login google or import file |
Mute Tab is completely not working. Please remove it. |
|
floccus can not work at the setting stage |
Hi |
Switch from adgaurd to uBlockOrigin |
Isnt there someone that knows the limitations of Fenix for Extensions? Basically: working:
not working probably never:
Check out my list of addons, all are actually useful but also not confusing, snake oil or simply not working. Most addons will download so this seperation makes little sense. So broken:
Useless, confusing, duplicates, snakeoil
Tracking / Bad addons
Some other addons have Chinese names or something I cant make a sense of like Nonio or Belfast Telegraph. So this was just a quick look. Guys please clean that list, its a total mess. Look at mine, I have even some missing ones. Dont follow the "I install 362 Addons so I am vewwy private" mania, every addon is an increased attack surface and can even track actively, or simply be useless, redundant, broken or even harmful. |
Lovely forks is also broken |
Copy tab title url is broken |
export tab urls shows an empty list |
External video player also broken, intent URLs dont work on Android |
Link Gopher is broken |
Pls update ✅️ |
EX // https://github.com/dessant/buster E // this extentions have an issue with the nativeMessaging permission and it is failing to install on Android S // mozilla-mobile#15904 Q // can anyone make a fix for that?? some old EXtentions not work at all or fail to install because of this... edit-fixed on 2.15.1 for this particular addon |
Duckduck go privacy essentials broken |
Now that we all can set our own addon collections to experiment (thanks, @abhijitvalluri), it might be a good time to review the default list of addons. Quite a lot of them refuse to install or don't do anything when installed.
I am thinking that all addons that arent installable at all should be removed from the default list. Stuff that installs but doesn't do anything is debatable.
What do you think about that?
The text was updated successfully, but these errors were encountered: