Announcement

Collapse
No announcement yet.

Firefox 72 Released With Picture-In-Picture Video Support Working On Linux

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • vladimir86
    replied
    I did use Firefox from 2006 till 2019, except a couple of years with SeaMonkey. Stopped with ver 68-69 because videos would constantly freeze while on fullscreen. Actually I had that problem years ago, but back them it was blamed on Flash... now I have no idea.

    Version 72 has the same issue. No matter if I used my Integrated Intel drivers or discrete AMD. Plus I always ad that annoying issue with videos playing at 480p and having to select 1080 manually on Youtube. I am not fan of Chromium, but I got really tired of waiting for a fix or trying to sort for this bug.

    Leave a comment:


  • sandy8925
    replied
    Originally posted by brainlet_pederson

    That's true, but Google is a much bigger company, where it's easier for the competent people to pick up the slack created by diversity hires...

    Google also has piles of cash to burn, whereas Mozilla is a one-product shop whose one product is becoming irrelevant. It won't be long before one of the Android bloatware browsers has a bigger market share than Firefox...
    I see that you're brainless pedersen, an idiot troll who hasn't achieved shit in their life, and can only talk down to others.

    Leave a comment:


  • sandy8925
    replied
    Originally posted by brainlet_pederson

    It makes perfect sense. They've been hiring based on diversity quotas and Adversity Olympics instead of technical excellence. Their downward spiral into irrelevance is a classic example of what happens to a company when they fill their ranks with mediocre SJWs.
    You're an idiot who hasn't bothered to read about Mozilla's history or take a look at who's working there.

    Leave a comment:


  • Djhg2000
    replied
    Perhaps the reason hiring programs aimed at anything but competence are allowed to keep going is that the real competence is on its way out anyway. We need Gecko to keep WebKit somewhat at bay, but now Gecko is eating memory like crazy anyway. There used to be Presto and Trident as well but they got killed in favor of WebKit. All we have left now for graphical browser engines are WebKit flavors, Gecko, KHTML on life support and Links2.

    Turns out we need diversity in browser engines, not competence. Since everything is turning into JavaScript kludge now anyways it's only a matter of time before WebKit really does become an operating system. Too bad it's what GNOME and Google wanted anyway.

    Not surprising since JavaScript is a garbage-oriented language with the learning curve of a stapler. We need to introduce C as a minimum bar for what qualifies as a professional programmer, perhaps then shooting yourself in the foot will start hurting again instead of causing a barely noticable performance regression on a workstation.

    But hey, as long as everyone can feel like they're contributing hot ideas to the dumpster fire there's no reason for them to ever get out of their comfort zone, right?

    Leave a comment:


  • 240Hz
    replied
    Originally posted by hax0r View Post
    Yes I enable:
    Code:
    layers.acceleration.force-enabled
    I was under impression that this causes H264 hardware decoding to be used during video playback? I know youtube is VP9 by default that's why I force AVC with h264ify. I might be totally wrong though, H264 HW decoding might be on Windows only.
    Your impression is wrong, this has nothing to do with video playback. This option is to hwaccel the UI. There is NO way to have hwaccel video playback on Firefox, the only way is to use chromium with the vaapi patch, afaik most distributions have chromium with the vaapi patch in their repositories

    Leave a comment:


  • caligula
    replied
    Originally posted by treba View Post
    Apart from the not-yet-existing hardware decoding on Linux, the Webrender issue for this is AFAIK https://bugzilla.mozilla.org/show_bug.cgi?id=1579235
    That looks horrible. This layer / hw acceleration stuff has taken way too long. I bought Baytrail and Cherrytrail Atom tablet/laptop some years ago and hoped that the perf issues will be fixed rather soonish. Well, here we are now, the devices are still horribly slow for browsing the web. FWIW, the Intel cstate bugs are still there https://bugzilla.kernel.org/show_bug.cgi?id=109051. I guess it's best to get rid of that crap and switch to ARM64/Android.

    Leave a comment:


  • caligula
    replied
    Originally posted by brainlet_pederson

    That's true, but Google is a much bigger company, where it's easier for the competent people to pick up the slack created by diversity hires...

    Google also has piles of cash to burn, whereas Mozilla is a one-product shop whose one product is becoming irrelevant. It won't be long before one of the Android bloatware browsers has a bigger market share than Firefox...
    Unless it affects the development somehow, I don't see why the market share matters. It's a bit silly to even talk about market when the product is free. At least on Linux, Firefox is still miles ahead Epiphany and other shit tier browsers.

    Leave a comment:


  • tildearrow
    replied
    Originally posted by brainlet_pederson

    It makes perfect sense. They've been hiring based on diversity quotas and Adversity Olympics instead of technical excellence. Their downward spiral into irrelevance is a classic example of what happens to a company when they fill their ranks with mediocre SJWs.
    Further proof is that the logo ball is no longer blue but purple, and that the font is a bit more "feminine" or "less-serious" (or that is how I explain it....)

    OK, I am not going to discuss about this anymore for now.

    Leave a comment:


  • hax0r
    replied
    Originally posted by xpris View Post

    How you can use hardware decoding if Firefox on Linux still not support it? Or maybe you taking on layers?
    Yes I enable:
    Code:
    layers.acceleration.force-enabled
    I was under impression that this causes H264 hardware decoding to be used during video playback? I know youtube is VP9 by default that's why I force AVC with h264ify. I might be totally wrong though, H264 HW decoding might be on Windows only.

    Leave a comment:


  • DoMiNeLa10
    replied
    Originally posted by DanL View Post

    The problem is not the evil, evil, SJW boogey(wo)men as you'd like to believe, but the problem is that Google and Mozilla just point their fingers to the assortment of video decode API's and drivers on Linux like they can't pick one or more and receive bug reports about them, even hidden behind a white/blacklist flag. They don't even try.
    That wasn't even the core of the argument in the first place, but whatever. It was about Firefox being quite irrelevant on the browser market.

    Leave a comment:

Working...
X