Oh, I so hope that goes upstream so it makes it into LibreWolf. 
3 Likes
I always apply the same patch to Firefox, Iceweasel and LibreWolf (with minor adjustments). So, once everything is ready (I really hope it will be), it will be applied to all Firefox fork
13 Likes
Ahoy @3dEyes
Thank you for your development !
I would add Floorp, as Firefox based browser, to the wishlist 
2 Likes
Unfortunately, Floorp has completely changed its build system, and building a new version will be very difficult
I see - thanks for your update about it.
What about that strategy they would do it ?
I mean you contact them, and informed them about
you started to work on Haiku native backend ?
They may do the hard work for us … ;- ))
and would work on a Haiku version of Floorp,
as I assume : the new code will be available from your side publicly …
It’s just shooting blindly from me,
I do not know it is possible to work out this way -
Let’s not rush things. The native backend is still in its very early stages and requires a lot of further development and testing. I might publish test builds in my LOTE repository in about a week - or maybe not. It all depends on a number of factors, such as available time and coding challenges
13 Likes
Really interesting, looking forward to see the results in a few weeks:)
Having FireFox is one first big step, but having a native GUI Firefox will be awesome !
2 Likes
It would be nice if hundreds of developers had the same idea and move to lighten software layers up (yes, I’m pointing my finger at LibreOffice, Eclipse, VLC…) instead of always releasing bigger, fatter, heavier applications.
Yet I know, cross-platform layers make things easier.
1 Like
VLC had a native BeOS frontend. It became too much for the then port maintainer (me) to update around the time of the early 0.8 versions, and was even losing features before then - the playlist stopped working in 0.7 or so.
The cross platform stuff sometimes ensures things stay up to date when there’s less resources available. We also had BeOS native Abiword once.
5 Likes
3 posts were split to a new topic: Firefox Telemetry & Tracking
Folks, please discuss your preferences and phobias in a separate thread. Personally, I couldn’t care less whether Mozilla knows what processor is installed on my motherboard. Whether or not you use the product—or which product you choose—is entirely up to you. My role is simply to provide you with that choice; I will continue to update the ports for all the forks whenever possible.
16 Likes
Currently implemented:
- Window creation and content rendering
- Mouse event handling
- Keyboard event handling (system keyboard layout input works;
modifier key handling requires refinement) - System theme integration (fonts and UI color scheme are derived from system Appearance settings)
To be implemented:
System shell integration module (opening files, opening directories in Tracker, setting default applications, setting desktop wallpaper)File dialogs (Open/Save via BFilePanel)System file icon reading moduleDrag-and-dropSystem clipboard
Issues to resolve (requiring analysis, debugging, and experimentation):
about:preferences settings are not displaying at all (only the settings sections appear)Audio playback is not working; the node is created, but the application crashes immediatelySome UI elements are rendering incorrectly (e.g., the VPN popup has incorrect dimensions)- Decide on the default scrollbar style (Windows, macOS, Android, GTK, or a custom rendering module)
I might have forgotten something else important, or something else might come up later
22 Likes
Very nice. The keyboard not working properly with wayland is one reason I did not even attempt to use firefox. It is good to see work on a more native frontend!
How exactly does the keyboard not work correctly in Wayland? How can the issue be reproduced?
Great movement!
It is very appealing goal for me to have more native behavior. But I was not brave to keep maintaining large patchset to moving target within my spare time.
I am happy if I help you to make this working for daily use. Any area can I assist you? Or should I help upstreaming existing patches (Sorry I should have done them before.)
Before that, I need upgrade my Haiku installation to beta 6.
9 Likes
Thank you for updating us, @3dEyes , above the coding efforts – we are appreciating your extra care for our appetite for sneak peeks !
1 Like
As I said, I’ve not attempted to use it. But there were lots of forum posts about this, for example not beeing able to input the “@” sign. Since I’ve not used it I can’t tell you if that issue is still present
The @ sign works perfectly fine now
1 Like
I don’t think the GTK+Wayland patches should be removed - the ability to build with different toolkits might prove useful, at least at this stage.
1 Like
This problem was solved long ago by dynamically translating the system keyboard layout into the xkb format.