Firefox For Android
Tula Difeo
i do know that it available in night and beta but i want to use release/stable version i do some config in firefox and when something happen in certain site i do not want to test if it related to one of my custom setting or a bug in beta/night version
Hi all, Just thought I would chime in here on the 1Password-Samsung-Android-Firefox issue. Obviously there is something buggy with this combination. In my case, 1Pasword & Firefox work together fine when my Samsung S9 phone with Firefox and Android 10 is set up according to the 1Password instructions found here: -filling/. However...not so much on my Samsung Galaxy Tab A 10 (SM-T510) with android 11 and Firefox. In that case, like others, I have also found that disabling Autofill and keeping only Accessibility on enables 1Password and Firefox to play nice together. I hope this helps others who are dealing with an issue that was driving me nuts. Also, I'm curious if the 1Password team has figured out what's going on here. From what I see on the web, it appears that the issue may be most common on Samsung devices?
We've recently identified an issue with a few websites in Firefox that no longer fill as expected. So far we've found Amazon, Twitter and Reddit are effected in Firefox but not Chrome or other supported browsers. We may need to wait for a fix from Firefox but we're continuing to investigate on our end as well: ref: android-1521
On my android device Firefox seems to bypass Pi-hole, I normally notice this because I see some ads and then realise pi.hole has stopped working as well as some other custom DNS entries that I have set up. If I then use a service to check the DNS being used (eg ) then Chrome and the default browser show my Pi whereas Firefox shows a Google DNS server.
Add-on does not install if navigate directly to file:/// URL:
It appears that Firefox has disabled installing unsigned extensions by directly navigating to a file:/// link (I have not yet tested signed extensions.). Thus, using the adb shell am start -a android.intent.action.VIEW method of using an intent to cause Firefox to navigate to the file:///mnt/sdcard/extentionFile.xpi URL will only bring up the "Blocked Add-on" dialog, without the option to allow, of which you have included a screenshot in your question. This dialog is the same if you manually type in the URL.
I have all that and a couple more on my desktop already and I have sync set up in both locations to the same account. On top of that, it also seems that between android devices, addon syncing also does not occur.
Before running your extension on Firefox for Android, consider using web-ext lint. Lint performs a check to determine if any of the permissions, manifest keys, and web extension APIs you're using are incompatible with Firefox for Android. Lint relies on your extension's manifest.json file including strict_min_version values for the optional gecko and gecko_android sub-keys in browser_specific_settings. It then reports on the features that are not supported by the minimum version you have set.
When setting strict_min_version values in browser_specific_settings, unless you're targeting a specific version of Firefox, choose the most recent version of Firefox you expect your extension to be compatible with. Due to Android's different APIs and form factors (compared to desktop Firefox), set gecko_android after explicitly verifying compatibility. This sub-key enables a compatibility range that is distinct from Firefox for desktop.
In the unzipped directory of your extension, run web-ext run -t firefox-android and follow the instructions on screen to make sure you select the right device. Select org.mozilla.fenix as the apkname (or org.mozilla.firefox_beta for Firefox Beta for Android).
There must be addons that are not compatible or hard to configure because of the screen size, YMMV! Here is a recent thread on what Fenix users are looking out for and some compatability reviews: _addons_do_you_most_want_to_see_on_firefox/
df19127ead