While I see there is a waterfox app on the playstore but it is very slow compared to the mozilla version of it.
Are there any plans for making a fork of the firefox-for-android project?
I may do so in the future, would seem like a good path to take Waterfox.
This will be released shortly, anything specific you'd like to see in the Android release?
As much changes from desktop version as possible.
Maybe a slight blue tint in the background surrounding the tabs.
Or instead of a slight blue tint it could reflect the color of the website icon or something like on mobile google chrome
And maybe release it on the F-droid store please..
Ideally I would love if it had a similar level of customization as the desktop version. I don't care for Firefox on Android much due mainly to the UI so ability to customize would be great. Give the ability for the user to change more settings and features around to make the browser how they most like it.
Even something simple like a userChrome.css to modify the UI would be a great start. I don't think this would be too tricky, there are many methods for altering views. Hardest part would be ensuring good performance and that the modifications aren't discarded with say a screen rotate. Maybe some sort of cached version of the layouts would be able to facilitate this but that's just a theory off the top of my head.
Released on F-Droid would be awesome.
Maybe view/delete individual cookies
https://gitlab.com/fdroid/rfp/issues/373 When will it be submitted to f-droid,
Thanks for the suggestions. Need to work a bit more on the Android version, it’s not so great at the moment.
It would be great if possible to port Desktop version fully to Android !!!
But if only modifying existent android version in plans, would like to suggest 'switching UI modes' or splitting them for elements to switch on/off :
https://github.com/MrAlex94/Waterfox/issues/359
This helps using tabs or more ui elements on smaller screen devices.
@D0ve, Firefox for Android used to be XUL based, but unfortunately the UX was not very good and was resource heavy, so Mozilla switched to using the native UI.
Things have changed on the smartphone landscape in terms of computing power - but I image the resources necessary to get a XUL based browser on mobile will be quite tough again.
Ironically the newer Firefox for Android versions look more awful and lags even more than the XUL-versions
@MrAlex94 Wow! Usual FF UI on Android,-really the greatest browser!!!
Because now - it's exist a big lack of ui elements in ANY Android browser(with their using native ui), they're just poor of elements and possibilities(((.
It will be one and only best browser for Android!!!
@MrAlex94 Might be that futured GreatFullUI android version should take implementation of UI scale future (for supporting various display resolution '"out-of-the-box").
I think will may take the extension smth. like that(plus needed 'scalling app ui' / 'scaling of icons' support):
https://addons.mozilla.org/en-US/firefox/addon/theme-font-size-changer/
Latest release 55.2 rather far behind other platforms.. think it shows by the crashes and mem iasuea..
The problem is that when you click Menu-Bookmarks or History then aforementioned pages are opened on behalf of current page instead of being opened in the new tab. Waterfox for Android.
Also yeah, crashes sometimes.
Now that it's released on the playstore, when will the f-droid version follow? There are foss f-droid builds of firefox already named "fennec". Using their source as reference could help for including ti into f-droid.
People with customs roms, region locks, etc. can't and/or don't want to use the proprietary playstore as package manager
@Serkan-devel
builds are planned in 'releases' section here ...
@D0ve on F-Droid or on the github page?
F-Droid is coming once I remove GP integrations.
Can this issue be left open until it's released?
on F-Droid or on the github page? >>>
@Serkan-devel
Imo logically both places, but firstly on f-droid, because need to get f-droid sign for android build;
but after on github too, because github place will include either other platform versions and non public release versions like betas, rc's , test's , etc.
Am I right , Alex ;) ?
@MrAlex94 and if possible, please, before close this issue take a look on this one https://github.com/MrAlex94/Waterfox/issues/359
I dunno exactly 3 or 2 android modes of ui interface type is hardcoded in it,
but apk somehow decides which one needed to switch 'on':
for tablet , for phablet or for smartphone (or only tablet and smartphone ).
Could you please investigate a little, is it possible just put thats apk decisions to about:config switch?
(btw this about:config switch could be happily used in a future to switch to another new desktop's xul interface on android for testing and/or using)
When will Waterfox be on F-Droid?
@Serkan-devel
I'm awaiting either, hope asap ;)
The patches have all been applied so I just need to patch and ship :-)
On Sat, 30 Jun 2018 at 17:02, Dove notifications@github.com wrote:
@Serkan-devel https://github.com/Serkan-devel
I'm awaiting either, hope asap ;)—
You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub
https://github.com/MrAlex94/Waterfox/issues/143#issuecomment-401549734,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEgoWOAZfgBlcaj5btUfzGxhjCOWx6slks5uB6EpgaJpZM4NBXkK
.
May be shoudn't close this issue ? ..., it's about inner Waterfox interface-more powerful , not
like native android...like now.
Btw, the link:
https://staging.f-droid.org/search?q=Waterfox&lang=en
is my favorite this summer ;) !!! Because google.play injects in their apks spyware((( !!!
When will it be shipped?
@DI555, there's no search results on F-Droid with the name Waterfox...
~Ibuprophen
I actually am still building the code base with all these new changes.
Removing the GPE integrations is chaos, but getting there!
On Thu, 26 Jul 2018 at 19:19, Ibuprophen notifications@github.com wrote:
@DI555 https://github.com/DI555, there's no search results on F-Droid
with the name Waterfox...~Ibuprophen
—
You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub
https://github.com/MrAlex94/Waterfox/issues/143#issuecomment-408188706,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEgoWBlVnATp-cGOKjIYf8Kb1aOHkVy1ks5uKggegaJpZM4NBXkK
.
@MrAlex94 any updates on this?
@Serkan-devel, it looks like you have an Android device that's ARM 32-bit. The Only version of the Waterfox app that's compatible with the Architecture for this device is the Beta version of the app and this is a bit tricky for seeing on the Play Store.
Please see the following post that reflects the 2 ways for obtaining this for your Android device.
https://github.com/MrAlex94/Waterfox/issues/730#issuecomment-421647220
Good Luck! :-)
~Ibuprophen
@ibuprophen1 but I also have an S6. And I'm rather waiting for a GP-free version but thanks
@MrAlex94 any ETA for the GCM free mobile version? At F-Droid we're waiting to process this request to include Waterfox. Using Waterfox on all my PCs and Laptops, I'd especially welcome it there 😉
@MrAlex94 , while we're waiting f-droid's version, could it be possible to place all the builds here on github in 'releases' (or here but in another repository especially for that), please!
You promissed;)?
@MrAlex94 , seems mozilla plans to drop fennec ((( ... and targeting on focus with geckoView....
Alex, could it be easier now to build full desktop FF version for android?
It will be great leap forward for mobile browser!!!
Maybe one could builld mobile versions of waterfox vased on fennec. F-droid has put some effort to free it from proprietary binaries so
@MrAlex94 more than a year ago, you wrote:
F-Droid is coming once I remove GP integrations.
How far has that progressed? I don't want to press, I ask because I'm triaging "old issues" on our end (F-Droid), and again came to the one asking to package Waterfox. Being a happy Waterfox user on Desktop, I'd really like to see that happen 😃
1.5 years later, 3rd triage run since my last post, RFP still sits waiting. Do we have a chance? Or do we need to :cry: and close that RFP as "unsolvable"? That would be a real pity.
Most helpful comment
I actually am still building the code base with all these new changes.
Removing the GPE integrations is chaos, but getting there!
On Thu, 26 Jul 2018 at 19:19, Ibuprophen notifications@github.com wrote: