As for now, the firefox binary complaints about pulseaudio if downloaded directly from mozilla.org.
(And the ancient -esr version is not for me)
I found out that the mozilla-firefox slackbuild for -current uses --enable-alsa.

I'm compiling the mozilla-firefox from -current to 14.2. Will take some time

Will report back if it works without pulseaudio :-)

It took roughly 35 minutes to compile firefox-52.0.1 on my machine. and sound works without pulseaudio! (Which it don't from the binary on mozilla.org)

Great ! :]

And now its in 14.2 "patches":

1 members found this post helpful.

Yep. Many thanks for adding 52.0.2 to the stable branch, Pat! I can now watch Netflix on all of my units without installing extra software.

1 members found this post helpful.

Ok nice. I recompiled 52.0.2 with gtk3 and --enable-alsa

what's the point with gtk2 anyway? It bugs out with youtube without flash when doing fullscreen... (on some, ancient, almost none-used windowmanager)

Would be nice if PV answered.

Thanks anyway volkerdi :-)

I think i will mark this as solved.

Best Regards, slacktroll

I think a firefox with gtk+3 will be a forced option in the future, as 53.x doesn't support building against gtk+2 anymore

I personally don't like it that much because of the different way of scrolling via the right position bar: with the gtk+2 version clicking up and down in the bar scrolls like a pager, with the gtk+3 version it goes directly to that position in the page.
when used with pages with progressive loading, like facebook for example, that way of scrolling becomes a little awkward...

1 members found this post helpful.

Where's the firefox 53.x versions? would be nice to try and compile =)
(I don't use facebook :/...)

Ohh.. found it.
https://archive.mozilla.org/pub/fire...53.0b8/source/
will try to compile :-)

note that to build firefox-53.x you will need to explicitly disable the rust sources with "--disable-rust" or you will need the additional dependencies (they will become mandatory with versions 54.x) rustc and cargo (I linked to the versions I'm testing here but you can also use the ones on SBo - rust and cargo).

1 members found this post helpful.

Another big problem is that the gtk3 firefox crashed with mozplugger, and there is no working alternative (kpartsplugin is obsolete, mozplugger crashes). Looks like firefox 52 will be the last usable version.

mozplugger, like all the others npapi plugins, will be obsoleted very soon, skaendo talked about it a few hours ago in another topic.

1 members found this post helpful.

According to a post on the Devuan list a couple of weeks ago, the ALSA support will be removed from Firefox. This has renewed interest in the apulse project which provides programs with a compatibility layer to use ALSA without Pulse Audio being installed. Some of the list members reported success using Firefox with apulse.

Thank you. compiling rust took VERY long time on my old quad core.

Rocking with firefox 53 now

Firefox ESR 52 will be the last version to support NPAPI plugins. The 52 ESR was released mid-march which means you have until April 2018 if you are a NPAPI plugin user (ESR lifetime is roughly one year). After April 2018, there will not be a maintained version of Firefox with NPAPI support.

2 members found this post helpful.

Maybe irrelevant for some, but after seeing a mozilla developer saying that it's my problem that I had telemetry disabled in the browser and that is why they can't officially support my machines anymore, maybe palemoon should be concidered. I have been using firefox for more than 17 years. I enabled telemetry so it sended anymore data they need ... and then went searching and finally installed palemoon from sbo. Really, besides this

https://forum.palemoon.org/viewtopic...fe4d6e#p109549

it reminded me why I was using firefox in the first place. It has the old style sane interface, the one with the small, more appropriate for desktop use tabs. It's like a blast from the past (a good one). So far everything seems to work. It is compatible with the firefox plugins i use (ublock origin and noscript), I haven't tested java though yet.
It crashes under KDE if I use oxygen-gtk as the gtk theme, so I had to change it in KDE settings. Other than that, it is exactly how firefox should be. Let's hope that it's stable enough, which it should be since it is based on mozilla sources.

This is pretty well known and easy to fix, just change your Pale Moon launcher command to point to a different gtk2 theme like so;

You can still use the oxygen-gtk theme for the rest of your system if you wish that way.