Yes i know it is not daily drivable stable bug-free one. It was my reason not to prioritize packaging until recently.
I will focus fixing bugs for myself because sharing builds are time consuming (for me) but bring almost no progress to project.
4 Likes
From my side it was absulutely NOT an urging post to have a fix imediately :j
It was just facts and statements a s I promised tests …
So I just provided my outputs to have something to investigate for devs as they have time for it.
I terribly sorry if I was misunderstandable in any way about the purpose of these posts recently from my side - -
Kind regards,
Thank you for the new version, I have installed it form LOTE on nightly build (58293)
Numeric pad problem still exists.
But the first problem with videos is solved !! Congrats !!
This is the first time I tried the Firefox port (super easy to install from the Lote repository), took less than 20 seconds to install it and all dependencies, and after a couple of minutes of visiting some of the heavier sites I visit, I must admit that the performance and stability is much better than what I expected. As a test version (with work in progress dependencies), it works surprisingly well. A few niggling issues that is to be expected for a work in progress port, eventually it should be on par with other OS ports.
Its funny to visit other sites and to see them autodetect Linux as the hosting browser OS. I do understand the browser id problems that some websites have, hence why the ID needs to be masquaraded to something they will accept. Cannot believe that this is still a thing in 2024.
Well done everyone involved with the project.
6 Likes
In fact, it was not intended. I noticed that recently. It is just the result we use the common UNIX variant code. We just didn’t add #ifdef __HAIKU__ for that logic yet.
But I plan to keep things as-is for a while. Because I don’t want to let sites detect our now-buggy browser misbehaves and block it at this stage. As it is too easy to just blocking relatively minor browser on minor platform when they feel harmful and it is harder to revert that blocking rule.
7 Likes
I agree.
We are looking for new names.
The first ones that come to mind:
Arcadia (from Captain Harlock)
Nostromo (from Alien)
Voyager (space probe)
Or something related to Haiku:
Haiku Navigator
Or something with a Japanese flavor:
Hokku (Short poem)
Yugen (Profound sense o mistery and beauty)
Wabi (Imperfect beauty)
I like Arcadia and some other ones are neat, hard pass on Hokku though, to me it sounds like a rare word or specialized language, as 句 means “(poem) stanza” (発句 - Jisho.org), if you want to go with poetry Waka, Tanka & other similar ones (Renga especially, as it is “linked verse”) would fit the bill much better imo, my blue chicken paisà 
Not a fan of Wabi either all things considered (侘び - Jisho.org). Judging by your definition I’d guess you’re actually thinking about “Wabisabi” (侘び寂び - Jisho.org). While I’m here I’m going to nitpick the fact that it’s actually “Yūgen” 
1 Like
can somebody write a post
IN PLAIN ENGLISH
about how one can use Firefox on Haiku
(all the necessary steps, terminal commands etc.)
please
Follow the instructions in this post, in other words install the custom Wayland server package then the (firefox) nightly package from LOTE.
If you use Haiku Nightly,it has become really easy.
Add the LOTE repository: pkgman add-repo https://www.haikuware.ru/repo/lote
Then install the nightly and wayland_server packages from this repository.
Replace the HaikuPorts wayland_server with the LOTE one,otherwise the window doesn’t update.
We are not looking for new names!
The developer "KENZ2 will choose bezilla or nightly or whatever!
1 Like
According to HaikuPorts, the current name is BeZilla.
Trying to compile as well from the current PR on HaikuPorts… and it’s very long (in progress) :
As “LTO” seems to be the last step, hope to have the compilation ok from this PR.
1 Like
Hi, great work.
Thank you.
It’s possible to port Firefox to 32Bit?
regards lorglas
Exactly. According to KENZ we’re going to use some temporary name (e.g. BeZilla) until we can call it Firefox:
1 Like
Ahoy folks,
I would use Nightly in R1B5 - I mean with added themes, addons etc I configured for it on Haiku Nightly - so I would copy that profile.
I checked first /boot/home/config/settings for Nightly or nightly, and Firefox or firefox - found nothing there.
Ok , so not adapted this way to Haiku. Right, I turned to Terminal to find with commands.
~> find /boot -name nightly
~> find /boot -name Nightly
/boot/system/data/deskbar/menu/Applications/Nightly
/boot/system/apps/Nightly
/boot/system/apps/Nightly/Nightly
~> find /boot -name Firefox
~> find /boot -name firefox
/boot/home/.mozilla/firefox
/boot/home/config/cache/mozilla/firefox
~>
Question :
Is that enough if I copy
/boot/home/.mozilla
and
/boot/home/config/cache/mozilla
(and the containing subdirs) onto Haiku R1B5
to have the same profile and run status on both installed Haiku ?
Kind regards,
1 Like
I would think you might have to change your profiles.ini to match whatever the default directory name is.
Package build after more than 13 hours on my NUC from the PR from Haiku Ports :
I don’t have sound (maybe something is missing), but except that BeZilla/Firefox is working fine :
10 Likes
I tried to install firefox nightly by executing
the commands:Install (double click) the files in this order to install:
- libnotify-0.8.1-2-x86_64.hpkg
- dbus_glib-0.112-1-x86_64.hpkg
-
pciutils-3.11.1-1-x86_64.hpkg - wayland_server-0.1.20230326-2-x86_64.hpkg
- nightly-128.1.0-2-x86_64.hpkg
command no 4 could not be executed
firefox appeared in the deskbar menu,
it opened, but froze
I have been using Haiku on raw metal,
on a Lenovo Thinkpad T410, for over a year,
64bit, of course,
beta 5 57937+125,
my system is updated at least once a week
I saved a firefox nightly report,
but it cannot be added here,
because of the file .report - extension
I uploaded the report in
Haiku channel on telegram
1 Like
Thank you for very time-consuming double checking my recipe works.
No sound and no JIT is expected as my branch does not have @3dEyes patches integrated yet.
I am currently trying to hack the wayland-server to support for firefox. It is required before I can publish firefox (I temporarily named as BeZilla) recipe. X512 looks busy these days, so I will extract minimal changes for firefox, fix some regressions and send PR.
Did you checked that Waddlesplash UNIX socket FD passing patch fixed Firefox IPC problems so workaround can be removed?
2 Likes