Mozilla Firefox For Android
Kenneth Calimlim
Give about:config to Firefox for Android and let us customize it the same way we can customize the desktop browser. That... high level of customization was the only reason I started using Firefox back in 2006 and why I still prefer Firefox for the desktop to any other browser.
I stopped using FF for Android 2 years ago because many pages simply won't load and hang in the middle of loading whereas the same pages open just fine and fast using Opera for Android. Since I was unable to send you feedback about that, I stopped using it. But now with Mozilla Connect I can share my ideas and hopefully bring FF for Android to the same glory its desktop cousin already has.
When I disabled IPv6 on the desktop Firefox last week, many of the pages suddenly started loading instantly bc my ISP, among many others in my country, still supports IPv4 only. So I'm 90% sure that if I can do the same with FF for Android, that will change its performance for the better. But it turned out that the mobile FF didn't have about:config.
-US/kb/difficulties-firefox-android-100
With the recommended fix for potential difficulties with Version 100 being an About:Config tweak, and Mozilla outright recommended Firefox Beta exclusively for the About:Config tweak, I think Mozilla themselves made the case for About:Config in Stable on Android better than any of us could.
If Mozilla can trust users of Stable Firefox on Desktop not to screw up About:Config, then they can trust users of Stable on Android too.
Me too, the arguments for removing this feature are very weak, about:config poses the same kind of "danger" on desktop as it does in my mobile phone. Why remove such a basic feature, which helped made Firefox what it is for years?
@Jonthanks for that info but
this should not be an idea from the beginning cause it should be there as it was for long time so no need to change to trending it should be implemented and that happen yesterday
hope to see it in the next update in android
I too searched for this and came across this thread.
I am aware of Fennec on F-Droid and the nightly & beta channels, but simply want to make pref changes with the stable release build just like I do with the desktop.
Mozilla don't have the market share of Chrome because they didn't spread Firefox aggressively and forcibly like Google did by integrating the browser installer into other software installers. If Mozilla did that, Chrome would drop out of the market share, LOL, bc the mass Windows user has the IQ of a vegetable and doesn't care what they click and what that clicking will do. They just click "next, next, next" and that's it.
Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!
I still wish there was an easier way to delete more than one bookmark though, like being able to highlight the ones you want and then just pressing delete. Apparently they're looking into adding such a function to android Firefox in the future so will have to wait for an update.
By everything he means all the data. Your chosen settings, browsing history, bookmarks, reading list, etc. Basically returning to a clean install without reinstalling.And to do that you go to Settings - Apps - Firefox - Storage. And hit [CLEAR DATA]
If you're not using Sync yet, you can always set it up just for the purpose of purging your bookmarks. But you'll need to sync it to a computer. And remember to sync it to a fresh Firefox profile. (run: "firefox.exe -p" if you want to make a new one)
You approach the coding of an extension for Firefox for Android in the same way as you would for a desktop extension; using a text editor or tool of your choice to write the code. However, when you want to test and debug your extension you need to follow a different process, this article walks you through that process.
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.
Before making your extension available, test it on Android to ensure it works as expected. When you publish it on AMO, reviewers may reject it or request changes if it doesn't meet basic usability requirements.
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).
Currently, you cannot inspect the markup of Fenix's browserAction popups using the Firefox Developer Tools Inspector (see bug 1637616). As a workaround, we recommend that you temporarily change the extension to open the popup extension page into a tab to be able to inspect it.
You can debug your extension in the web developer tools and view any manifest.json validation messages using adb logcat. To make use of these features, first set up Firefox remote debugging over USB or via Wi-Fi.
If prompted, allow the incoming connection on your Android device. Now start your extension on the Android device using web-ext run. You will need to have at least one tab opened in order for your extension to load. Click your device in the left-hand column and scroll down to find Processes in the list of active features in the browser.
For much of the debugging work, it's useful to be able to view Console with Inspector or Debugger. You do this using the split console, press esc to activate this mode.
In the Debugger you can set breakpoints, step through code, modify the extension's state, and do everything else you'd expect to be able to do in a debugger. Any messages logged by your code display in Console.
To inspect the popup's HTML and CSS, use Inspector. First, click the page select icon () to open the HTML document you want to inspect. You can review and modify the document's HTML and CSS in Inspector, as you would with any webpage.
In addition to the messages from your code, the console may also include messages about the validation of the extension's manifest.json files. These messages can be viewed using the adb logcat command. To avoid receiving other unrelated messages, you can pipe the output through grep, filtering by the extension's ID. For example:
Firefox for Android doesn't have full feature parity with the desktop version of Firefox. There are several known issues with Firefox for Android that can lead to a poor user experience. Therefore, it's recommended you use Manifest V2 for extensions targeting Firefox for Android.
59fb9ae87f