I've just checked Firefox 67.0 source code and found no evidence of hw-accelerated decoding. Firefox uses part of FFmpeg source code under the name "ffvpx", for VP9. There are some remainders of such…
Nope. It's just software decoders from FFmpeg project that are heavily optimized. Also Firefox disables VP9 on slower machines, so websites serve H.264 instead.
> Crashes occasionally Looks like Mozilla decided to ditch Flash, and now Firefox 40 sometimes hangs completely due to some odd interlocking with plugin-container process. > Main advantage ... is that accelerated…
Hanging on going to full screen is surely not an application fault, it's something with either X server or a video driver. File dialogs should work, for both loading and saving files.
"This" does; browser part is supported. To make it work, you'll need to get libpepflashplayer.so file from Chromebook, as only version from ChromeOS have DRM code compiled in.
I've just checked Firefox 67.0 source code and found no evidence of hw-accelerated decoding. Firefox uses part of FFmpeg source code under the name "ffvpx", for VP9. There are some remainders of such…
Nope. It's just software decoders from FFmpeg project that are heavily optimized. Also Firefox disables VP9 on slower machines, so websites serve H.264 instead.
> Crashes occasionally Looks like Mozilla decided to ditch Flash, and now Firefox 40 sometimes hangs completely due to some odd interlocking with plugin-container process. > Main advantage ... is that accelerated…
Hanging on going to full screen is surely not an application fault, it's something with either X server or a video driver. File dialogs should work, for both loading and saving files.
"This" does; browser part is supported. To make it work, you'll need to get libpepflashplayer.so file from Chromebook, as only version from ChromeOS have DRM code compiled in.