[firefox] why is firefox compiled with webrtc disabled?

[Nikita790]

hey guys so I was wondering why Firefox was compiled with webrtc disabled. And I am also suggesting a firefox-webrtc package, if there is good resion for it to be disabled in the normal package, thank you.

[mogwai]

That question has been asked a few times without a response. I've also seen at least one pull request on the PKGBUILDs on github which was rejected without reason.

My suspicion is that enabling webrtc pushes the build outside of what the build infrastructure is capable of in terms of memory usage. If so, then it's a bit of an arbitrary choice: it's probably possible to compile firefox (within the same contstraints) with webrtc by disabling some other feature. On the other hand, I wouldn't know which other feature to disable that wouldn't impact functionality...

Anyway, it must be a build constraint because I can happily build firefox with webrtc (from the exact same PKGBUILD) on a 8GB RPI in both an aarch64 and armv7h userland. It's a similar thing for chromium: the official armv7h package is still on an old version (85) while I can compile the latest version (87) myself without any issue.
So these days I'm usually building my own packages for firefox, chromium and thunderbird.

PS: If any of the developers/moderators are reading this, I'm open to helping out: by building the packages or maybe just sharing access to the build host?